[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f703f960702061724o51e2cdadi28ae367c2b3029cb@mail.gmail.com>
Date: Tue, 6 Feb 2007 16:24:37 -0900
From: "Kent Overstreet" <kent.overstreet@...il.com>
To: "Davide Libenzi" <davidel@...ilserver.org>
Cc: "Joel Becker" <Joel.Becker@...cle.com>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Zach Brown" <zach.brown@...cle.com>,
"Ingo Molnar" <mingo@...e.hu>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
linux-aio@...ck.org, "Suparna Bhattacharya" <suparna@...ibm.com>,
"Benjamin LaHaise" <bcrl@...ck.org>
Subject: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
> 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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists