public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amerigo Wang <amwang@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	Neil Horman <nhorman@redhat.com>,
	Andi Kleen <andi@firstfloor.org>,
	akpm@linux-foundation.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC Patch 1/2] kexec: show memory info in /proc/iomem
Date: Wed, 12 Aug 2009 10:15:55 +0800	[thread overview]
Message-ID: <4A8225DB.8040008@redhat.com> (raw)
In-Reply-To: <m1eirhlryf.fsf@fess.ebiederm.org>

Eric W. Biederman wrote:
> Amerigo Wang <amwang@redhat.com> writes:
>
>   
>>> Nacked-by: "Eric W. Biederman" <ebiederm@xmission.com>
>>>
>>> We can inspect the image we are going to load to get this information.
>>> In fact /sbin/kexec already inspects the image we are going to load
>>> to get this information.  Putting this in the kernel adds kernel
>>> complexity for no gain.
>>>   
>>>       
>> /sbin/kexec is supported to know this, of course. But this is not for
>> /sbin/kexec, this is for user (or other programs) to observe the memory
>> information, so that he can know the memory he reserved is too much or not.
>>     
>
>   
>> Without this, it is a little hard to use patch 2/2.
>>     
>
> So add on option to /sbin/kexec.
>   

This can be another choice.
> Furthermore none of this does a good job of predicting how much
> memory /sbin/fsck will require to check the filesystem before we
> write a crash dump.
>   

No one actually knows this without testing... But if 128M on x86 is 
still not enough, that is probably a bug of fsck, not our fault.


  reply	other threads:[~2009-08-12  2:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 10:39 [RFC Patch 1/2] kexec: show memory info in /proc/iomem Amerigo Wang
2009-08-11 10:39 ` [RFC Patch 2/2] kexec: allow to shrink reserved memory Amerigo Wang
2009-08-11 10:46   ` Neil Horman
2009-08-11 20:55     ` Yu, Fenghua
2009-08-12  1:32     ` Amerigo Wang
2009-08-11 19:57   ` Eric W. Biederman
2009-08-12  1:25     ` Amerigo Wang
2009-08-12  1:46       ` Eric W. Biederman
2009-08-12  2:08         ` Amerigo Wang
2009-08-12  2:43           ` Eric W. Biederman
2009-08-12  3:14             ` Amerigo Wang
2009-08-11 19:49 ` [RFC Patch 1/2] kexec: show memory info in /proc/iomem Eric W. Biederman
2009-08-12  1:17   ` Amerigo Wang
2009-08-12  1:51     ` Eric W. Biederman
2009-08-12  2:15       ` Amerigo Wang [this message]
2009-08-12  2:39         ` Eric W. Biederman
2009-08-11 20:50 ` Yu, Fenghua
2009-08-12  1:27   ` Amerigo Wang

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=4A8225DB.8040008@redhat.com \
    --to=amwang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nhorman@redhat.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