mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mala Anand" <manand@us.ibm.com>
To: dipankar@beaverton.ibm.com
Cc: BALBIR SINGH <balbir.singh@wipro.com>,
	linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
	lse-tech-admin@lists.sourceforge.net,
	Paul McKenney <Paul.McKenney@us.ibm.com>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [Lse-tech] Re: [RFC] Dynamic percpu data allocator
Date: Mon, 3 Jun 2002 14:12:29 -0500	[thread overview]
Message-ID: <OF60D095C7.87A83057-ON85256BCD.0068BA3A@raleigh.ibm.com> (raw)

On Thu, May 30, 2002 at 08:56:36AM -0500, Mala Anand wrote:
>>

>>                       dipankar@beaverton.ibm.co

>>                       m                                To:       BALBIR
SINGH <balbir.singh@wipro.com>
>>
>>The per-cpu data allocator allocates one copy for *each* CPU.
>> >It uses the slab allocator underneath. Eventually, when/if we have
>> >per-cpu/numa-node slab allocation, the per-cpu data allocator
>> >can allocate every CPU's copy from memory closest to it.
>>
>> Does this mean that memory allocation will happen in "each" CPU?
>> Do slab allocator allocate the memory in each cpu? Your per-cpu
>> data allocator sounds like the hot list skbs that are in the tcpip stack
>> in the sense it is one level above the slab allocator and the list is
>> kept per cpu.  If slab allocator is fixed for per cpu, do you still
>> need this per-cpu data allocator?

>Actually I don't know for sure what plans are afoot to fix the slab
allocator
>for per-cpu. One plan I heard about was allocating from per-cpu pools
>rather than per-cpu copies. My requirements are similar to
>the hot list skbs. I want to do this -

I looked at the slab code, per cpu slab is already implemented by Manfred
Spraul.
Look at cpu_data[NR_CPUS] in kmem_cache_s structure.


Regards,
    Mala


   Mala Anand
   E-mail:manand@us.ibm.com
   Linux Technology Center - Performance
   Phone:838-8088; Tie-line:678-8088




             reply	other threads:[~2002-06-03 19:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03 19:12 Mala Anand [this message]
2002-06-03 19:48 ` Dipankar Sarma
  -- strict thread matches above, loose matches on Subject: below --
2002-06-04 21:11 Paul McKenney
2002-06-04 12:05 Mala Anand
2002-05-30 13:56 Mala Anand
2002-05-30 17:55 ` Dipankar Sarma
2002-05-31  7:57   ` BALBIR SINGH
2002-05-31  8:40     ` Dipankar Sarma
2002-05-24  6:13 Dipankar Sarma
2002-05-24  8:38 ` [Lse-tech] " BALBIR SINGH
2002-05-24  9:13   ` Dipankar Sarma
2002-05-24 11:59     ` BALBIR SINGH
2002-05-24 14:38   ` Martin J. Bligh

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=OF60D095C7.87A83057-ON85256BCD.0068BA3A@raleigh.ibm.com \
    --to=manand@us.ibm.com \
    --cc=Paul.McKenney@us.ibm.com \
    --cc=balbir.singh@wipro.com \
    --cc=dipankar@beaverton.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech-admin@lists.sourceforge.net \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=rusty@rustcorp.com.au \
    /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®