public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Al Viro" <viro@ZenIV.linux.org.uk>
Cc: <ccache@lists.samba.org>, "Theodore Ts'o" <tytso@mit.edu>,
	"Sam Ravnborg" <sam@ravnborg.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Recent change to kernel spikes out ccache/distcc
Date: Wed, 07 Jan 2009 14:40:30 +0000	[thread overview]
Message-ID: <4964CCEE.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20090107143711.GW28946@ZenIV.linux.org.uk>

>>> Al Viro <viro@ZenIV.linux.org.uk> 07.01.09 15:37 >>>
>On Wed, Jan 07, 2009 at 02:28:10PM +0000, Jan Beulich wrote:
>> >	b) is there any reason why we can't copy symbol table out of module
>> >ourselves (instead of setting SHF_ALLOC on it) and trim the crap out of
>> >it?  Note that __crc_... is not the only junk in there - you don't need
>> >(or want) to keep the things like undefs for /proc/kallsyms purposes.
>> >And modules *using* an exported symbol are more common that modules exporting
>> >one...  Why not copy it at add_kallsyms() time, skipping the junk we don't
>> >want anyway?
>> 
>> Would certainly be doable, but would seem reasonable only if it's a small
>> set of easily recognizable symbols. If you look at scripts/strip-symbols,
>> you may agree that it's better to do this at build time...
>
>I will not.  Undefined ones are far more common than any of those...

Undefined ones could certainly be stripped out there (while they definitely
can't be at build time).

Jan


  reply	other threads:[~2009-01-07 14:40 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 15:15 [REGRESSION] Recent change to kernel spikes out ccache/distcc Theodore Ts'o
2009-01-06 15:29 ` Jan Beulich
2009-01-06 17:33   ` Theodore Tso
2009-01-06 17:48     ` Sam Ravnborg
2009-01-06 18:04       ` Theodore Tso
2009-01-07  8:50     ` Jan Beulich
2009-01-07 11:31       ` Sam Ravnborg
2009-01-07 12:35         ` Jan Beulich
2009-01-07 13:23           ` Sam Ravnborg
2009-01-07 13:48             ` Jan Beulich
2009-01-07 20:06               ` Sam Ravnborg
2009-01-08 19:16                 ` Kyle McMartin
2009-01-12 14:06                 ` Gilles Espinasse
2009-01-06 17:53   ` Sam Ravnborg
2009-01-06 16:26 ` David Miller
2009-01-06 18:12   ` Theodore Tso
2009-01-06 22:09 ` Sam Ravnborg
2009-01-07  4:33   ` Theodore Tso
2009-01-07  5:10 ` Al Viro
2009-01-07  8:49   ` Jan Beulich
2009-01-07 14:03     ` Al Viro
2009-01-07 14:28       ` Jan Beulich
2009-01-07 14:37         ` Al Viro
2009-01-07 14:40           ` Jan Beulich [this message]
2009-01-07 13:12 ` Theodore Tso
2009-01-07 13:39   ` Jan Beulich
2009-01-07 14:28     ` Theodore Tso
2009-01-07 14:39       ` Jan Beulich
2009-01-08 19:17   ` Dave Jones
2009-01-08 21:31     ` Theodore Tso
2009-01-11 21:48       ` Kyle McMartin
2009-01-11 22:11         ` Theodore Tso
2009-01-11 22:51         ` Theodore Tso
2009-01-11 22:55           ` Kyle McMartin
2009-01-14 17:16 ` Peter Zijlstra
2009-01-15  9:11   ` Jan Beulich
2009-01-15 13:40     ` Theodore Tso

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=4964CCEE.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=ccache@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tytso@mit.edu \
    --cc=viro@ZenIV.linux.org.uk \
    /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