mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Adrian Bunk <bunk@stusta.de>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
	linux-kernel@vger.kernel.org,
	Fastboot mailing list <fastboot@lists.osdl.org>
Subject: Re: strange CRASH_DUMP dependencies
Date: Mon, 22 Aug 2005 18:56:49 -0600	[thread overview]
Message-ID: <m18xyto4ha.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050822204417.GI9927@stusta.de> (Adrian Bunk's message of "Mon, 22 Aug 2005 22:44:17 +0200")

Adrian Bunk <bunk@stusta.de> writes:

>> > - Is there any sane reason for the dependency on EMBEDDED?
>> > 
>> 
>> I believe this was introduced because large servers can have huge amount
>> of memory (running into Tera Bytes) and saving all that memory might not be
>> practical. Hence it was perceived that until some filtering mechanism is
>> implemented, it is more suited for small systems.
>>...
>
> It seems you have a wrong impression of what EMBEDDED in the kernel 
> does.
>
> There is _not_ a choice EMBEDDED/WORKSTATION/SERVER.
>
> EMBEDDED is an option that shows "save space at any cost" options.
>
> It allows you to tell gcc to generate slower but faster code or to 
> deselect options in the "do this only if you _really_ know what you are 
> doing" class.

And at the moment that is where building a crashdump capture kernel falls.
"do this only if you really know what you are doing". 

Eric


  reply	other threads:[~2005-08-23  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 22:53 Adrian Bunk
2005-08-22  6:23 ` Vivek Goyal
2005-08-22  6:40   ` Eric W. Biederman
2005-08-22 20:44   ` Adrian Bunk
2005-08-23  0:56     ` Eric W. Biederman [this message]
2005-08-23  7:14     ` Vivek Goyal

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=m18xyto4ha.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=bunk@stusta.de \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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
Powered by JetHome