From: Christoph Hellwig <hch@lst.de>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make kmem_find_general_cachep static in slab.c
Date: Tue, 7 Sep 2004 18:52:21 +0200 [thread overview]
Message-ID: <20040907165221.GA11383@lst.de> (raw)
In-Reply-To: <413DE6C9.5050402@colorfullife.com>
On Tue, Sep 07, 2004 at 06:50:17PM +0200, Manfred Spraul wrote:
> Why?
> It's intended for users that want to kmalloc always the same amount of
> memory.
> For example the network layer could call kmem_find_general_cachep once
> for dev->mtu and then just call kmem_cache_alloc instead of kmalloc. The
> loop in kmalloc often needs more cpu cycles than the actual alloc.
Because there's no single user, and for constant size arguments kmalloc
already optimizes very well, so I rather doubt people are ever going to
use this one.
Is the basic don't design APIs for a maybe future scheme.
prev parent reply other threads:[~2004-09-07 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 14:36 [PATCH] make kmem_find_general_cachep static in slab.c Christoph Hellwig
2004-09-07 16:50 ` Manfred Spraul
2004-09-07 16:52 ` Christoph Hellwig [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=20040907165221.GA11383@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.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