From: Oleg Verych <olecom@flower.upol.cz>
To: Adrian Bunk <bunk@kernel.org>
Cc: Denys Vlasenko <vda.linux@googlemail.com>,
sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] build system: section garbage collection for vmlinux
Date: Thu, 6 Sep 2007 23:16:15 +0200 [thread overview]
Message-ID: <E1ITOhz-0001wd-Uu@flower> (raw)
In-Reply-To: <20070906203931.GE4480@stusta.de>
* Thu, 6 Sep 2007 22:39:31 +0200
[]
>> > His patch improves the build process.
>>
>> I would like to know timing, btw. Size, especially shown 1%, doesn't
>> matter if link time increased dramatically. `Allyes' config, when i
>> had fast and rammish machine was terrible thing (last winter). If 32
>> cores/cpus is will of author, then i'm even more suspicious.
>
> For non-developers size and speed of the kernel matter much more than
> compile time.
I'm talking about benefits for the process (developers, testers) and
the result (end users, dogs eating own food :).
> When you go towards embedded systems with limited resources a 1% size
> decrease would often be worth it even if it would (hypothetically)
> increase the compile time by a factor of 10.
text data bss dec hex filename
5159478 1005139 406784 6571401 644589 linux-2.6.23-rc4.org/vmlinux
5131822 996090 401439 6529351 63a147 linux-2.6.23-rc4.gc/vmlinux
Are this numbers show embedded target? I think no. Also time factor of
*10* can be spent more productively reviewing actual code of parts, that
are going to be embedded, no?
[]
>> > There's nothing that requires treatment.
>>
>> [Help for] The developers/contributors of those drivers, no?
>>...
>
> They did everything right.
>
> You should better try to understand the problem first before behaving as
> if you knew everything better than everyone else...
OK, thank you very much. Now, describe what problem you are talking
about, please. I see non.
____
next prev parent reply other threads:[~2007-09-06 21:01 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 13:43 [PATCH 0/3] build system: section garbage collection for vmlinux Denys Vlasenko
2007-09-05 13:47 ` [PATCH 1/3] " Denys Vlasenko
2007-09-05 13:49 ` [PATCH 2/3] " Denys Vlasenko
2007-09-05 13:55 ` [PATCH 3/3] " Denys Vlasenko
2007-09-05 18:40 ` Denys Vlasenko
2007-09-05 20:46 ` Sam Ravnborg
2007-09-06 10:55 ` Denys Vlasenko
2007-09-06 22:33 ` Sam Ravnborg
2007-09-10 12:01 ` Sam Ravnborg
2007-09-10 19:02 ` Denys Vlasenko
2007-09-10 19:14 ` Sam Ravnborg
2007-09-11 11:23 ` Denys Vlasenko
2007-09-11 11:55 ` Sam Ravnborg
2007-09-05 20:07 ` [PATCH 1/3] " Sam Ravnborg
2007-09-06 10:59 ` Denys Vlasenko
2007-09-06 22:36 ` Sam Ravnborg
2007-09-08 15:02 ` Denys Vlasenko
2007-09-05 15:53 ` [PATCH 0/3] " Oleg Verych
2007-09-05 18:46 ` Denys Vlasenko
2007-09-05 20:34 ` Oleg Verych
2007-09-05 21:52 ` Adrian Bunk
2007-09-06 10:55 ` Denys Vlasenko
2007-09-06 11:40 ` Oleg Verych
2007-09-06 12:21 ` Adrian Bunk
2007-09-06 20:43 ` Oleg Verych
2007-09-06 20:39 ` Adrian Bunk
2007-09-06 21:16 ` Oleg Verych [this message]
2007-09-06 21:19 ` Adrian Bunk
2007-09-06 22:01 ` Oleg Verych
2007-09-06 22:43 ` Adrian Bunk
2007-09-06 12:33 ` Denys Vlasenko
2007-09-05 16:29 ` Daniel Walker
2007-09-05 18:37 ` Denys Vlasenko
2007-09-05 18:38 ` Daniel Walker
2007-09-05 19:14 ` Denys Vlasenko
2007-09-05 19:07 ` Daniel Walker
2007-09-05 19:49 ` Denys Vlasenko
2007-09-05 19:46 ` Daniel Walker
2007-09-06 10:57 ` Denys Vlasenko
2007-09-06 15:13 ` Daniel Walker
2007-09-06 17:07 ` Denys Vlasenko
2007-09-07 16:31 ` Daniel Walker
2007-09-07 17:24 ` Sam Ravnborg
2007-09-07 17:19 ` Daniel Walker
2007-09-07 17:30 ` Denys Vlasenko
2007-09-07 17:38 ` Daniel Walker
2007-09-05 19:31 ` Adrian Bunk
2007-09-05 19:24 ` Daniel Walker
2007-09-05 19:46 ` Adrian Bunk
2007-09-05 19:27 ` Adrian Bunk
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=E1ITOhz-0001wd-Uu@flower \
--to=olecom@flower.upol.cz \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vda.linux@googlemail.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