If that's what is wanted, then the async_submit() API can detect the
syncronous completion soon, and drop a result inside the result-queue
immediately. It means that an immediately following async_wait() will find
some completions soon. Or:
struct async_submit {
void *cookie;
int sysc_nbr;
int nargs;
long args[ASYNC_MAX_ARGS];
};
struct async_result {
void *cookie;
long result:
};
int async_submit(struct async_submit *a, struct async_result *r, int n);
Where "r" will store the ones that completed syncronously. I mean, there
are really many ways to do this.
That interface (modifying async_submit to pass in the size of the result array) would work great. - 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: 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: Davide Libenzi <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- Prev by Date: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- Next by Date: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- 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):
 |