Messages in this thread | | | Date | Tue, 13 Feb 2007 23:32:20 +0100 | From | Andi Kleen <> | Subject | Re: [patch 00/11] ANNOUNCE: "Syslets", generic asynchronous system call support |
| |
On Tue, Feb 13, 2007 at 11:26:26PM +0100, Ingo Molnar wrote: > > * Andi Kleen <andi@firstfloor.org> wrote: > > > > really, what's the point behind aio_cancel()? > > > > The main use case is when you open a file requester on a network file > > system where the server is down and you get tired of waiting and press > > "Cancel" it should abort the hanging IO immediately. > > ok, that should work fine already - exit in the user context gets
That would be a little heavy handed. I wouldn't expect my GUI program to quit itself on cancel. And requiring it to create a new thread just to exit on cancel would be also nasty.
And of course you cannot interrupt blocked IOs this way right now (currently it only works with signals in some cases on NFS)
-Andi - 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/
| |