From: Mike Christie <michaelc@cs.wisc.edu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stefani Seibold <stefani@seibold.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
open-iscsi@googlegroups.com
Subject: Re: [RFC 0/2] new kfifo API
Date: Mon, 03 Aug 2009 11:41:14 -0500 [thread overview]
Message-ID: <4A77132A.4080005@cs.wisc.edu> (raw)
In-Reply-To: <200908031642.15136.arnd@arndb.de>
On 08/03/2009 09:42 AM, Arnd Bergmann wrote:
> On Monday 03 August 2009, Stefani Seibold wrote:
>> This is a proposal of a new generic kernel FIFO implementation.
>>
>> The current kernel fifo API is not very widely used, because it has to many
>> constrains. Only 13 files in the current 2.6.30 used it. FIFO's are
>> like list are a very basic thing and a kfifo API which handles the most use
>> case would save a lot of time and memory resources.
>>
>> I think there are the following reasons why kfifo is not in use.
>>
>> - There is a need of a spinlock despite you need it or not
>> - A fifo can only allocated dynamically
>> - There is no support for data records inside a fifo
>> - The FIFO size can only a power of two
For iscsi, the only thing we have not liked with the current code is
having to have the fifo a power of 2. It has not been that big a deal
though.
next prev parent reply other threads:[~2009-08-03 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 13:39 [RFC 0/2] new kfifo API Stefani Seibold
2009-08-03 14:42 ` Arnd Bergmann
2009-08-03 15:14 ` Stefani Seibold
2009-08-03 18:23 ` Arnd Bergmann
2009-08-03 18:45 ` Stefani Seibold
2009-08-03 16:41 ` Mike Christie [this message]
2009-08-03 18:27 ` Andi Kleen
2009-08-03 18:35 ` Arnd Bergmann
2009-08-03 18:48 ` Stefani Seibold
2009-08-03 19:00 ` Arnd Bergmann
2009-08-03 19:48 ` Stefani Seibold
2009-08-04 12:24 ` Arnd Bergmann
2009-08-04 12:44 ` Stefani Seibold
2009-08-04 13:45 ` Arnd Bergmann
2009-08-04 14:57 ` Stefani Seibold
2009-08-04 18:00 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A77132A.4080005@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=open-iscsi@googlegroups.com \
--cc=stefani@seibold.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.