On 12/28/06, Evgeniy Polyakov <johnpol@xxxxxxxxxxx> wrote:
[ I'm only subscribed to linux-fsdevel@ from above Cc list, please keep this list in Cc: for AIO related stuff. ] On Wed, Dec 27, 2006 at 04:25:30PM +0000, Christoph Hellwig (hch@xxxxxxxxxxxxx) wrote: > (1) note that there is another problem with the current kevent interface, > and that is that it duplicates the event infrastructure for it's > underlying subsystems instead of reusing existing code (e.g. > inotify, epoll, dio-aio). If we want kevent to be _the_ unified > event system for Linux we need people to help out with straightening > out these even provides as Evgeny seems to be unwilling/unable to > do the work himself and the duplication is simply not acceptable. I would rewrite inotify/epoll to use kevent, but I would strongly prefer that it would be done by peopl who created original interfaces - it is politic decision, not techinical - I do not want to be blamed on each corner that I killed other people work :) FS and network AIO kevent based stuff was dropped from kevent tree in favour of upcoming project (description below). According do AIO - my personal opinion is that AIO should be designed asynchronously in all aspects. Here is brief note on how I plan to iplement it (I plan to start in about a week after New Year vacations). === All existing AIO - both mainline and kevent based lack major feature - they are not fully asyncronous, i.e. they require synchronous set of steps, some of which can be asynchronous. For example aio_sendfile() [1] requires open of the file descriptor and only then aio_sendfile() call. The same applies to mainline AIO and read/write calls. My idea is to create real asyncronous IO - i.e. some entity which will describe set of tasks which should be performed asynchronously (from user point of view, although read and write obviously must be done after open and before close), for example syscall which gets as parameter destination socket and local filename (with optional offset and length fields), which will asynchronously from user point of view open a file and transfer requested part to the destination socket and then return opened file descriptor (or it can be closed if requested). Similar mechanism can be done for read/write calls. This approach as long as asynchronous IO at all requires access to user memory from kernels thread or even interrupt handler (that is where kevent based AIO completes its requests) - it can be done in the way similar to how existing kevent ring buffer implementation and also can use dedicated kernel thread or workqueue to copy data into process memory.
Would you have time to comment on the approach I have taken to implement a standard asynchronous memcpy interface? It seems it would be a good complement to what you are proposing. The entity that describes the aio operation could take advantage of asynchronous engines to carry out copies or other transforms (maybe an acrypto tie in as well). Here is the posting for 2.6.19. There has since been updates for 2.6.20, but the overall approach remains the same. intro: http://marc.theaimsgroup.com/?l=linux-raid&m=116491661527161&w=2 async_tx: http://marc.theaimsgroup.com/?l=linux-raid&m=116491753318175&w=2 Regards, Dan - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
