mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@quark.didntduck.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Anton Blanchard <anton@samba.org>,
	Brian Gerst <bgerst@didntduck.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] slab.c cleanup
Date: Sun, 23 Mar 2003 16:07:37 -0500	[thread overview]
Message-ID: <3E7E2219.5090501@quark.didntduck.org> (raw)
In-Reply-To: <3E7E204C.2040700@colorfullife.com>

Manfred Spraul wrote:
> Anton wrote:
> 
>>> - Don't create caches that are not multiples of L1_CACHE_BYTES.
>>
>>
>> Nice idea, I often see the list walk (of the cache sizes) in kmalloc 
>> in kernel
>> profiles. eg a bunch of kmalloc(2k) for network drivers.
>>
>> Since we have a 128byte cacheline on ppc64 this patch should reduce that.
>>  
>>
> No, the patch is a bad thing: It means that everyone who does 
> kmalloc(32,) now allocates 128 bytes, i.e. 3/4 wasted. IMHO not acceptable.

Perhaps, but it currently is already allocating 128 bytes for smaller 
caches, because the cache is created with SLAB_HWCACHE_ALIGN.  So we 
ended up with redundantly sized caches.

--
				Brian Gerst


  reply	other threads:[~2003-03-23 20:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-23 20:59 Manfred Spraul
2003-03-23 21:07 ` Brian Gerst [this message]
2003-03-23 21:20   ` Manfred Spraul
2003-03-23 21:51     ` Brian Gerst
     [not found] <20030323211010$1215@gated-at.bofh.it>
     [not found] ` <20030323211014$2f0c@gated-at.bofh.it>
2003-03-23 21:24   ` Arnd Bergmann
     [not found] <20030323191010$7678@gated-at.bofh.it>
2003-03-23 21:11 ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2003-03-23 18:58 Brian Gerst
2003-03-23 19:12 ` Anton Blanchard

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=3E7E2219.5090501@quark.didntduck.org \
    --to=bgerst@quark.didntduck.org \
    --cc=anton@samba.org \
    --cc=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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®