From: Adrian Bunk <bunk@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: acme@redhat.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add EXPORT_SYMBOL(ksize);
Date: Mon, 3 Dec 2007 14:57:00 +0100 [thread overview]
Message-ID: <20071203135700.GR15974@stusta.de> (raw)
In-Reply-To: <200712032041.ABB90643.SOFVQFtMHFLOOJ@I-love.SAKURA.ne.jp>
On Mon, Dec 03, 2007 at 08:41:44PM +0900, Tetsuo Handa wrote:
> Hello.
>
> Arnaldo Carvalho de Melo wrote:
> > > But I think ksize() should be available to kernel modules as well as kmalloc() etc.
> > Why do you think so? You have to justify that with some valid use.
> Is there an alternative function?
The question is not whether there's an alternative function.
The kernel does not waste memory for all users by providing a fixed API
for external modules, the purpose of the kernel is to provide everything
required for what is shipped with the kernel.
Simply send the patch adding the exports when you submit your module for
inclusion in the kernel.
> If not, it sounds to me that this is a regression.
That sounds strange considering that slab and slob AFAIR never exported
this symbol and only slub in 2.6.22 and 2.6.23 exports it.
> We couldn't know how much memory was allocated by kmalloc() in 2.4 era, and we can know it 2.6 era.
> But are we going back to 2.4 era for out-of-tree kernel modules?
The interesting fact is that there are zero in-kernel modules using it.
> Thanks.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-12-03 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 8:43 [PATCH] Add EXPORT_SYMBOL(ksize); Tetsuo Handa
2007-12-02 13:48 ` Adrian Bunk
2007-12-02 21:34 ` Tetsuo Handa
2007-12-02 21:46 ` Arnaldo Carvalho de Melo
2007-12-03 11:41 ` Tetsuo Handa
2007-12-03 13:57 ` Adrian Bunk [this message]
2007-12-03 14:07 ` Pekka Enberg
2007-12-03 21:19 ` Matt Mackall
2007-12-03 23:34 ` Andrew Morton
2007-12-06 21:02 ` Adrian Bunk
2007-12-06 21:07 ` Adrian Bunk
2007-12-11 10:46 ` Bernd Schmidt
2007-12-11 11:16 ` Greg Ungerer
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=20071203135700.GR15974@stusta.de \
--to=bunk@kernel.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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;
as well as URLs for NNTP newsgroup(s).