From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
WANG Chao <chaowang@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/4] x86, kdump: Set crashkernel_low automatically
Date: Sun, 14 Apr 2013 18:59:59 -0700 [thread overview]
Message-ID: <516B5F1F.1040106@zytor.com> (raw)
In-Reply-To: <1365749691-21299-2-git-send-email-yinghai@kernel.org>
On 04/11/2013 11:54 PM, Yinghai Lu wrote:
> + /*
> + * two parts from lib/swiotlb.c:
> + * swiotlb size: user specified with swiotlb= or default.
> + * swiotlb overflow buffer: now is hardcoded to 32k,
> + * round to 8M to cover more others.
> + */
This comment is incomprehensible. "Cover more others"?
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2013-04-15 2:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 6:54 [PATCH -v5 0/4] x86, kdump: Fix crashkernel high with old kexec-tools Yinghai Lu
2013-04-12 6:54 ` [PATCH v5 1/4] x86, kdump: Set crashkernel_low automatically Yinghai Lu
2013-04-15 1:59 ` H. Peter Anvin [this message]
2013-04-15 2:59 ` Yinghai Lu
2013-04-15 3:26 ` H. Peter Anvin
2013-04-12 6:54 ` [PATCH v5 4/4] kexec: use Crash kernel for Crash kernel low Yinghai Lu
2013-04-12 6:54 ` [PATCH v5 2/4] x86, kdump: Retore crashkernel= to allocate under 896M Yinghai Lu
2013-04-12 6:54 ` [PATCH v5 3/4] x86, kdump: Change crashkernel_high/low= to crashkernel=,high/low Yinghai Lu
2013-04-15 0:20 ` HATAYAMA Daisuke
2013-04-12 20:07 ` [PATCH -v5 0/4] x86, kdump: Fix crashkernel high with old kexec-tools 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=516B5F1F.1040106@zytor.com \
--to=hpa@zytor.com \
--cc=chaowang@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=yinghai@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.