From: Stefani Seibold <stefani@seibold.net>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] kfifo: round up the fifo size power of 2
Date: Fri, 26 Oct 2012 15:39:46 +0200 [thread overview]
Message-ID: <1351258786.10060.5.camel@wall-e> (raw)
In-Reply-To: <20121026123321.GG2778@yliu-dev.sh.intel.com>
Am Freitag, den 26.10.2012, 20:33 +0800 schrieb Yuanhan Liu:
> On Fri, Oct 26, 2012 at 11:30:27AM +0200, Stefani Seibold wrote:
> > Am Freitag, den 26.10.2012, 15:56 +0800 schrieb Yuanhan Liu:
> > > 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.
> > > ----
> > > I know it works with rounddown_pow_of_two as well, since size is maintained
> > > in the kfifo internal part. But, I'm quite curious why Stefani chose
> > > rounddown_pow_of_two. To reduce memory?
> > >
> >
> > Yes, exactly, if a user do the wrong thing, than the user will get also
> > a wrong result, and did not waste memory.
>
> But, isn't it better to 'correct' it? ;-)
Both is wrong. This depends on the view. For me it is better to get less
and don't wast space. For example: requesting 1025 will yield in your
case to a fifo which 2048 elements, which requires double of the memory
as expected.
>
> >
> > But anyway, if the majority like this patch it is okay for me.
>
> Sorry, do you mean you are OK with this patch?
>
I depends not on me, ask for a democratic decisions.
Greetings,
Stefani
next prev parent reply other threads:[~2012-10-26 13:40 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 [this message]
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
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=1351258786.10060.5.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