linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefani Seibold <stefani@seibold.net>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] kfifo: round up the fifo size power of 2
Date: Wed, 31 Oct 2012 07:30:33 +0100	[thread overview]
Message-ID: <1351665033.23165.6.camel@wall-e> (raw)
In-Reply-To: <20121031055916.GC29509@yliu-dev.sh.intel.com>

Am Mittwoch, den 31.10.2012, 13:59 +0800 schrieb Yuanhan Liu:
> On Mon, Oct 29, 2012 at 01:59:35PM -0700, Andrew Morton wrote:
> > On Fri, 26 Oct 2012 15:56:57 +0800
> > Yuanhan Liu <yuanhan.liu@linux.intel.com> wrote:
> > 
> > > Say, if we want to allocate a filo with size of 6 bytes, it would be safer
> > > to allocate 8 bytes instead of 4 bytes.
> > >
> > > ...
> > >  	if (!is_power_of_2(size))
> > > -		size = rounddown_pow_of_two(size);
> > > +		size = roundup_pow_of_two(size);
> > >  
> > >  	fifo->in = 0;
> > >  	fifo->out = 0;
> > 
> > hm, well, if the user asked for a 100-element fifo then it is a bit
> > strange and unexpected to give them a 128-element one.
> 
> 
> Yes, and I guess the same to give them a 64-element one.
> 
> > 
> > If there's absolutely no prospect that the kfifo code will ever support
> > 100-byte fifos then I guess we should rework the API so that the caller
> > has to pass in log2 of the size, not the size itself.  That way there
> > will be no surprises and no mistakes.
> > 
> > That being said, the power-of-2 limitation isn't at all intrinsic to a
> > fifo, so we shouldn't do this.  Ideally, we'd change the kfifo
> > implementation so it does what the caller asked it to do!
> 
> I'm fine with removing the power-of-2 limitation. Stefani, what's your
> comment on that?
> 

You can't remove the power-of-2-limitation, since this would result in a
performance decrease (bit wise and vs. modulo operation).

Andrew is right, this is an API miss design.  So it would be good to
rework the kfifo_init () and kfifo_alloc() to pass in log2 of the size,
not the size itself.

Stefani



  reply	other threads:[~2012-10-31  6:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26  7:56 [PATCH 1/2] kfifo: round up the fifo size power of 2 Yuanhan Liu
2012-10-26  7:56 ` [PATCH 2/2] kfifo: handle the case that alloc size is equal to 0 Yuanhan Liu
2012-10-26  9:30 ` [PATCH 1/2] kfifo: round up the fifo size power of 2 Stefani Seibold
2012-10-26 12:33   ` Yuanhan Liu
2012-10-26 13:39     ` Stefani Seibold
2012-10-26 14:06       ` Yuanhan Liu
2012-10-26 14:23       ` Alan Cox
2012-10-29 20:59 ` Andrew Morton
2012-10-31  5:59   ` Yuanhan Liu
2012-10-31  6:30     ` Stefani Seibold [this message]
2012-10-31  6:49       ` Yuanhan Liu
2012-10-31 20:31         ` Stefani Seibold
2012-10-31  6:52       ` Andrew Morton
2012-10-31  8:11         ` Janne Kulmala
2012-10-31 11:16           ` Andrew Morton
2012-10-31 20:31         ` Stefani Seibold
2012-11-08 12:24         ` Yuanhan Liu
2012-11-08 12:37           ` Stefani Seibold
2012-11-09  2:32             ` Yuanhan Liu
2012-11-14  7:03               ` Stefani Seibold
2012-11-15  8:18                 ` Yuanhan Liu

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=1351665033.23165.6.camel@wall-e \
    --to=stefani@seibold.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuanhan.liu@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).