Messages in this thread | | | Date | Fri, 9 Feb 2007 11:02:28 +0530 | From | "Bharata B Rao" <> | Subject | Re: -mm merge plans for 2.6.21 |
| |
Andrew,
On 2/9/07, Andrew Morton <akpm@linux-foundation.org> wrote: > fsaio-add-a-wait-queue-arg-to-the-wait_bit-action-routine.patch > fsaio-add-a-wait-queue-arg-to-the-wait_bit-action-routine-gfs2-fix.patch > fsaio-rename-__lock_page-to-lock_page_blocking.patch > fsaio-interfaces-to-initialize-and-to-test-a-wait-bit-key.patch > fsaio-add-a-default-io-wait-bit-field-in-task-struct.patch > fsaio-enable-wait-bit-based-filtered-wakeups-to-work-for-aio.patch > fsaio-enable-wait-bit-based-filtered-wakeups-to-work-for-aio-fix.patch > fsaio-enable-wait-bit-based-filtered-wakeups-to-work-for-aio-fix-sparse-fix.patch > fsaio-enable-asynchronous-wait-page-and-lock-page.patch > fsaio-filesystem-aio-read.patch > fsaio-aio-o_sync-filesystem-write.patch > > Will wait to see what happens with febrils. > > aio-is-unlikely.patch > > Will merge. > > rework-compat_sys_io_submit.patch > fix-aioh-includes.patch > fix-access_ok-checks.patch > make-good_sigevent-non-static.patch > make-good_sigevent-non-static-fix.patch > make-__sigqueue_free-and.patch > aio-completion-signal-notification.patch > aio-completion-signal-notification-fix.patch > aio-completion-signal-notification-fixes-and-cleanups.patch > aio-completion-signal-notification-small-cleanup.patch > add-listio-syscall-support.patch > > I guess these are dependent upon fsaio.
No. AIO completion signal notification patches and listio patch work independently of fsaio patches. Just that for buffered AIO case, the fsaio patches will make the behaviour truly asynchronous.
Regards, Bharata. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |