An idiot using my keyboard wrote:
- AIO requests that are serviced from cache ought to immediately invoke the callback, in the same thread context as the caller, fixing up the stack so that the callback returns to the instruction following the syscall. That way the "immediate completion" path through the callback can manipulate data structures, allocate memory, etc. just as if it had followed a synchronous call.
Or, of course: if (async_stat(entry) == 0) { ... immediate completion code path ... } Ugh. But I think the discussion about the delayed path still holds. - Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: "Kent Overstreet" <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Davide Libenzi <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Joel Becker <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Davide Libenzi <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Joel Becker <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Davide Libenzi <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Joel Becker <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: "Michael K. Edwards" <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: "Michael K. Edwards" <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- Prev by Date: Re: [patch 1/3 take2] smaps: extract pte walker from smaps code
- Next by Date: Re: Slower CPU frequency reported by the kernel
- Previous by thread: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- Next by thread: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- Index(es):