From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: rusty@rustcorp.com.au
Cc: Tim Abbott <tabbott@ksplice.com>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-modules@vger.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 3/4] module: unexport each_symbol()
Date: Sat, 26 Sep 2009 13:13:35 +0100 [thread overview]
Message-ID: <4ABE056F.6090005@tuffmail.co.uk> (raw)
In-Reply-To: <20090923220022.GB30818@infradead.org>
Christoph Hellwig wrote:
> On Wed, Sep 23, 2009 at 01:29:43PM -0400, Tim Abbott wrote:
>
>> While Ksplice is not in-tree yet, Ksplice is a user of each_symbol (and in
>> fact was the reason why each_symbol was originally exported). Is it easy
>> to modify your patch series so that you don't have to remove each_symbol?
>>
>
> We don't keep symbols for out of tree junk around.
>
We do alter them mercilessly though :-).
I don't want to preserve the current implementation of each_symbol()
because it duplicates too much of the modified find_symbol(). However,
the duplicated code can be simplified if I changed the various "syms"
fields in struct module with a single array (without increasing the size
of struct module). I consider this a cleanup; it would benefit a couple
of other sites in module.c as well.
The change would make "struct symsearch" redundant - changing the
interface of each_symbol(). If Ksplice fails to merge quickly enough it
will still be easy to remove each_symbol(), and we'll still benefit from
the cleanup in find_symbol() and elsewhere.
Rusty, does that make sense to you?
Thanks
Alan
next prev parent reply other threads:[~2009-09-26 12:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 13:38 module: Speed up symbol resolution during module loading Alan Jenkins
2009-09-22 13:38 ` [PATCH 1/4] module: extract __ExPORT_SYMBOL from module.h into mod_export.h Alan Jenkins
2009-09-22 14:42 ` Sam Ravnborg
2009-09-22 14:45 ` Alan Jenkins
2009-09-22 15:45 ` Daniel Walker
2009-09-22 15:50 ` Alan Jenkins
2009-09-22 15:55 ` Daniel Walker
2009-09-22 13:38 ` [PATCH 2/4] kbuild: sort the list of symbols exported by the kernel (__ksymtab) Alan Jenkins
2009-09-22 14:48 ` Sam Ravnborg
2009-09-22 15:08 ` Alan Jenkins
2009-09-23 17:38 ` Sam Ravnborg
2009-09-22 13:38 ` [PATCH 3/4] module: unexport each_symbol() Alan Jenkins
2009-09-23 17:29 ` Tim Abbott
2009-09-23 18:36 ` Alan Jenkins
2009-09-23 22:00 ` Christoph Hellwig
2009-09-24 0:15 ` Rusty Russell
2009-09-26 12:13 ` Alan Jenkins [this message]
2009-09-22 13:38 ` [PATCH 4/4] module: speed up find_symbol() using binary search on the builtin symbol tables Alan Jenkins
2009-09-23 17:28 ` [PATCH 0/2] Use generic binary search function Tim Abbott
2009-09-23 18:08 ` Alan Jenkins
2009-09-23 17:28 ` [PATCH 1/2] lib: Add generic binary search function to the kernel Tim Abbott
2009-09-24 0:11 ` Rusty Russell
2009-09-27 17:05 ` Tim Abbott
2009-11-03 15:14 ` Thiago Farina
2009-11-03 15:34 ` Alan Jenkins
2009-09-23 17:28 ` [PATCH 2/2] module: use bsearch in find_symbol_in_kernel_section Tim Abbott
-- strict thread matches above, loose matches on Subject: below --
2009-09-22 13:28 module: Speed up symbol resolution during module loading Alan Jenkins
2009-09-22 13:28 ` [PATCH 3/4] module: unexport each_symbol() Alan Jenkins
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=4ABE056F.6090005@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=hch@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.org \
--cc=rusty@rustcorp.com.au \
--cc=tabbott@ksplice.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;
as well as URLs for NNTP newsgroup(s).