mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Martin Peschke <mp3@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch] statistics infrastructure - update 10
Date: Thu, 13 Jul 2006 01:00:04 -0700	[thread overview]
Message-ID: <20060713010004.63215f02.akpm@osdl.org> (raw)
In-Reply-To: <1152722709.3028.28.camel@dyn-9-152-230-71.boeblingen.de.ibm.com>

On Wed, 12 Jul 2006 18:45:08 +0200
Martin Peschke <mp3@de.ibm.com> wrote:

> On Wed, 2006-07-12 at 09:10 -0700, Andrew Morton wrote:
> > On Wed, 12 Jul 2006 14:27:39 +0200
> > Martin Peschke <mp3@de.ibm.com> wrote:
> > 
> > > +#define statistic_ptr(stat, cpu) \
> > > +	((struct percpu_data*)((stat)->data))->ptrs[(cpu)]
> > 
> > This would be the only part of the kernel which uses percpu_data directly -
> > everything else uses the APIs (ie: per_cpu_ptr()).  How come?
> 
> The API, i.e. per_cpu_ptr(), doesn't allow to assign a value to any of
> the pointers in struct percpu_data. I need that capability because I
> make use of cpu hotplug notifications to fix per-cpu data at run time.

Fair enough, I guess.

> With regard to memory footprint this is much more efficient than using
> alloc_percpu().

How much storage are we talking about here?  I find it a bit hard to work
that out.

> Is it be preferable to add something like set_per_cpu_ptr() to the API?

hm.  Add a generic extension to a generic interface within a specific
subsystem versus doing it generically.  Hard call ;)


I'd suggest that you:

- Create a new __alloc_percpu_mask(size_t size, cpumask_t cpus)

- Make that function use your newly added

	percpu_data_populate(struct percpu_data *p, int cpu, size_t size, gfp_t gfp);

	(maybe put `size' into 'struct percpu_data'?)

- implement __alloc_percpu() as __alloc_percpu_mask(size, cpu_possible_map)

- hack around madly until it compiles on uniprocessor.

  reply	other threads:[~2006-07-13  8:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 12:27 Martin Peschke
2006-07-12 16:10 ` Andrew Morton
2006-07-12 16:45   ` Martin Peschke
2006-07-13  8:00     ` Andrew Morton [this message]
2006-07-13 11:12       ` Martin Peschke
2006-07-13 14:43         ` Andrew Morton
2006-07-24 17:15           ` Martin Peschke

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=20060713010004.63215f02.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mp3@de.ibm.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

all inboxes | Powered by JetHome®