public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Nick Piggin <npiggin@suse.de>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Manfred Spraul <manfred@colorfullife.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/6] slab: introduce __kfree_rcu
Date: Mon, 23 Mar 2009 16:59:38 +0100	[thread overview]
Message-ID: <20090323155938.GA27151@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0903230931570.4095@qirst.com>


* Christoph Lameter <cl@linux-foundation.org> wrote:

> On Mon, 23 Mar 2009, Pekka Enberg wrote:
> 
> > > +static inline void *portion_to_obj(void *portion)
> > > +{
> > > +	struct page *page = virt_to_head_page(portion);
> > > +	struct slab *slab = page_get_slab(page);
> > > +	struct kmem_cache *cache = page_get_cache(page);
> > > +	unsigned int offset = portion - slab->s_mem;
> > > +	unsigned int index = offset / cache->buffer_size;
> > > +
> > > +	return index_to_obj(cache, slab, index);
> > > +}
> >
> > A minor nit: I think this would be more readable if you separated
> > variable declarations from the initializations. Also, you can probably
> > drop the inline from the function declaration and let GCC decide what to
> > do.
> 
> Thats debatable. I find the setting up a number of variables that 
> are all dependend in the above manner very readable. They are 
> usually repetitive. Multiple functions use similar 
> initializations.

I agree with Pekka, it's clearly more readable when separated out 
nicely:

	struct kmem_cache *cache;
	unsigned int offset;
	unsigned int index;
	struct page *page;
	struct slab *slab;

	page	= virt_to_head_page(portion);
	slab	= page_get_slab(page);
	cache	= page_get_cache(page);

	offset	= portion - slab->s_mem;
	index	= offset / cache->buffer_size;

The original form is hard to read due to lack of structure.

	Ingo

  reply	other threads:[~2009-03-23 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 13:44 [PATCH -mm 1/6] slab: introduce __kfree_rcu Lai Jiangshan
2009-03-23  7:48 ` Pekka Enberg
2009-03-23 13:33   ` Christoph Lameter
2009-03-23 15:59     ` Ingo Molnar [this message]
2009-03-23 16:40       ` Christoph Lameter
2009-03-23 16:56         ` Ingo Molnar
2009-03-23 17:49           ` Pekka Enberg
2009-03-23 18:06             ` Christoph Lameter
2009-03-23 18:59               ` Pekka Enberg
2009-03-23 19:06                 ` Christoph Lameter

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=20090323155938.GA27151@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=npiggin@suse.de \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=peterz@infradead.org \
    /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