linux-kernel - Re: [PATCH v5 1/4] x86, kdump: Set crashkernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9c406d9c-e69c-4d09-bdfc-6cecb53f373a@email.android.com>
Date:	Sun, 14 Apr 2013 20:26:12 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	WANG Chao <chaowang@...hat.com>,
	Vivek Goyal <vgoyal@...hat.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 1/4] x86, kdump: Set crashkernel_low automatically

Then make the comment so it is actually possible to understand that.

Yinghai Lu <yinghai@...nel.org> wrote:

>On Sun, Apr 14, 2013 at 6:59 PM, H. Peter Anvin <hpa@...or.com> wrote:
>> 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"?
>
>i mean other buffers that may need to stay low, but we do not know
>them eactly yet.
>
>Thanks
>
>Yinghai

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/