From: Tejun Heo <tj@kernel.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] percpu section full of holes
Date: Mon, 8 Jun 2015 12:15:43 +0900 [thread overview]
Message-ID: <20150608031543.GC21465@mtj.duckdns.org> (raw)
In-Reply-To: <20150608030932.GB21465@mtj.duckdns.org>
On Mon, Jun 08, 2015 at 12:09:32PM +0900, Tejun Heo wrote:
> For things we want to pack together, I suppose our only option is
> packing them into a struct and defining access macros into it. It's
> unfortunately clumsier but expresses the intended effect clearer to
> both readers and toolchain.
One annoying thing is that we prolly have quite a few places where
people put things which are likely to be used together close to each
other intentionally and by convention and we're now losing all that
contextual information. I have no idea whatsoever whether the gain
from toolchain shuffling symbols around is larger or smaller than
whatever gain which can be gained from such colocations.
Thanks.
--
tejun
prev parent reply other threads:[~2015-06-08 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 16:55 Eric Dumazet
2015-06-08 3:09 ` Tejun Heo
2015-06-08 3:15 ` Tejun Heo [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=20150608031543.GC21465@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®