From: Jay Lan <jlan@sgi.com>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: Neil Horman <nhorman@redhat.com>,
kexec@lists.infradead.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] makedumpfile: Shrink the time for creating 1st-bitmap (Re: problems in kdump kernel if 'maxcpus=1' not specified?)
Date: Fri, 18 Jul 2008 08:57:25 -0700 [thread overview]
Message-ID: <4880BD65.3030907@sgi.com> (raw)
In-Reply-To: <48801557.1040709@mxs.nes.nec.co.jp>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Ken'ichi Ohmichi wrote:
> Hi,
>
> Jay Lan wrote:
>> Ken'ichi Ohmichi wrote:
>>> Hi Jay,
>>>
>>> Ken'ichi Ohmichi wrote:
>>>> I created the attached patch that makedumpfile does not scan
>>>> memory gap when creating 1st-bitmap. Could you please try it ?
>>>> This patch is for makedumpfile-1.2.6.
>>> I found a bug in the patch I sent before, and I fixed it in the
>>> attached patch. Could you please try this patch ?
>>> Sorry for my mistake.
>> Hi Ken'ichi San,
>>
>> Thanks for your patch. I need to compete for the test machine. Will
>> post new data when i have one.
>
> I think that new makedumpfile (version 1.2.7) is more useful for you,
> because it includes not only this patch but also the other patch
> shrinking the time for creating bitmap.
I certainly will, Ken'ichi. Thanks!
I am eager to see the new data; unfortunately the test machine is
booked up until 7/29. :(
Regards,
- jay
>
>
> Thanks
> Ken'ichi Ohmichi
>
>
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-18 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 1:07 problems in kdump kernel if 'maxcpus=1' not specified? Jay Lan
2008-07-16 15:12 ` Vivek Goyal
2008-07-16 15:25 ` Neil Horman
2008-07-16 16:23 ` Vivek Goyal
2008-07-16 17:03 ` Neil Horman
2008-07-16 19:16 ` Jay Lan
2008-07-17 4:59 ` Ken'ichi Ohmichi
2008-07-17 6:35 ` [PATCH] makedumpfile: Shrink the time for creating 1st-bitmap (Re: problems in kdump kernel if 'maxcpus=1' not specified?) Ken'ichi Ohmichi
2008-07-17 17:09 ` Jay Lan
2008-07-18 4:00 ` Ken'ichi Ohmichi
2008-07-18 15:57 ` Jay Lan [this message]
2008-07-16 18:00 ` problems in kdump kernel if 'maxcpus=1' not specified? Jay Lan
2008-07-16 15:26 ` Bernhard Walle
2008-07-16 16:34 ` Vivek Goyal
2008-07-16 16:45 ` Bernhard Walle
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=4880BD65.3030907@sgi.com \
--to=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.com \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vgoyal@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