From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [PATCH] RCU: remove alignment padding from rcu_data on 64 bit builds
Date: Sun, 8 May 2011 07:53:23 -0700 [thread overview]
Message-ID: <20110508145323.GS2641@linux.vnet.ibm.com> (raw)
In-Reply-To: <1304684036.1998.10.camel@castor.rsk>
On Fri, May 06, 2011 at 01:13:56PM +0100, Richard Kennedy wrote:
> On Fri, 2011-05-06 at 08:20 +0200, Eric Dumazet wrote:
> ...
> > We could shrink this structure more, converting some 64bit fields to
> > 32bit ones.
> >
> > Rationale is the algo is working well on 32bit arches, no need to use
> > 64bit fields.
> >
> > candidates : completed, gpnum, passed_quiesc_completed, qlen,
> > qlen_last_fqs_check, blimit.
> >
> > Counters might be converted too.
>
> I don't know the code well enough to make that decision ;)
> Is it possible to shrink it enough to free up another cache line ?
> (16 longs to ints).
A number of these could be changed from long to int, though appropriate
adjustments need to be made. Some of the fields could be placed under
#ifdef CONFIG_RCU_TRACE, though again, corresponding adjustments would
need to be made.
> CONFIG_NO_HZ adds 24 bytes so even for users with !CONFIG_NO_HZ the
> variables you suggest are not enough to free a cache line.
Yep. And recent work introducing RCU priority boosting adds some more.
But it is not like this structure is allocated as a unit, so are you
really all that sensitive to the exact size?
Thanx, Paul
prev parent reply other threads:[~2011-05-08 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 15:50 [PATCH] RCU: remove alignment padding from rcu_data on 64 bit builds Richard Kennedy
2011-05-06 6:20 ` Eric Dumazet
2011-05-06 12:13 ` Richard Kennedy
2011-05-08 14:53 ` Paul E. McKenney [this message]
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=20110508145323.GS2641@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@rsk.demon.co.uk \
/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