public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Shaohua Li <shaohua.li@intel.com>,
	lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	"Chen, Tim C" <tim.c.chen@intel.com>
Subject: Re: [PATCH 1/2]percpu: introduce read mostly percpu API
Date: Wed, 20 Oct 2010 14:42:12 -0700	[thread overview]
Message-ID: <4CBF6234.9090402@zytor.com> (raw)
In-Reply-To: <4CBF616E.1080501@zytor.com>

On 10/20/2010 02:38 PM, H. Peter Anvin wrote:
> On 10/20/2010 12:53 AM, Eric Dumazet wrote:
>>
>> My question was more a rethoric one. I understand for sure the intent.
>>
>> All this should be explained in changelog, so that people know
>> when/where use this new class of per_cpu variables ;)
>>
> 
> Changelog really isn't the best place for this, a Documentation file
> would be better.
> 
> I'm trying to grok the intended semantic of the shared_aligned section
> right now... I'm not sure if there is a significant difference between
> the read mostly and the shared aligned section?
> 

>From the looks of it, it's a manual way to do what the linker would,
quite frankly, do better with SORT_BY_ALIGNMENT() -- although by
separating it out it might still be a win to avoid lots of "N+1"-sized
sections aligned to N.

	-hpa


  reply	other threads:[~2010-10-20 21:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20  3:07 [PATCH 1/2]percpu: introduce read mostly percpu API Shaohua Li
2010-10-20  5:18 ` Eric Dumazet
2010-10-20  6:00   ` H. Peter Anvin
2010-10-20  7:35   ` Andi Kleen
2010-10-20  7:53     ` Eric Dumazet
2010-10-20 21:38       ` H. Peter Anvin
2010-10-20 21:42         ` H. Peter Anvin [this message]
2010-10-20 21:33   ` H. Peter Anvin
2010-10-20 23:06 ` [tip:x86/mm] percpu: Introduce a read-mostly " tip-bot for Shaohua Li
2010-10-21  1:38   ` Shaohua Li
2010-10-21  2:53     ` H. Peter Anvin
2010-10-21  5:33     ` Eric Dumazet
2010-10-21  5:54       ` H. Peter Anvin
2010-10-21  6:07         ` Eric Dumazet
2010-10-21  6:09           ` H. Peter Anvin
2010-10-21  6:17             ` Shaohua Li
2010-10-21  6:48               ` Eric Dumazet
2010-10-21  6:54                 ` H. Peter Anvin
2010-10-21  6:10   ` H. Peter Anvin
2010-10-21  7:40 ` [tip:x86/mm] x86-32, percpu: Correct the ordering of the percpu readmostly section tip-bot for H. Peter Anvin

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=4CBF6234.9090402@zytor.com \
    --to=hpa@zytor.com \
    --cc=andi@firstfloor.org \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shaohua.li@intel.com \
    --cc=tim.c.chen@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