[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070530072617.GB3077@elte.hu>
Date: Wed, 30 May 2007 09:26:17 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Zach Brown <zach.brown@...cle.com>
Cc: Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Arjan van de Ven <arjan@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@....com.au>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Ulrich Drepper <drepper@...hat.com>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
"David S. Miller" <davem@...emloft.net>,
Suparna Bhattacharya <suparna@...ibm.com>,
Davide Libenzi <davidel@...ilserver.org>,
Jens Axboe <jens.axboe@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Syslets, Threadlets, generic AIO support, v6
* Zach Brown <zach.brown@...cle.com> wrote:
> > Having async request and response rings would be quite useful, and
> > most closely match what is going on under the hood in the kernel and
> > hardware.
>
> Yeah, but I have lots of competing thoughts about this.
note that async request and response rings are implemented already in
essence: that's how FIO uses syslets. The linked list of syslet atoms is
the 'request ring' (it's just that 'ring' is not a hard-enforced data
structure - you can use other request formats too), and the completion
ring is the 'response ring'.
Ingo
-
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