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] [thread-next>] [day] [month] [year] [list]
Message-Id: <200612141958.40519.s0348365@sms.ed.ac.uk>
Date:	Thu, 14 Dec 2006 19:58:40 +0000
From:	Alistair John Strachan <s0348365@....ed.ac.uk>
To:	Theodore Tso <tytso@....edu>, thunder7@...all.nl,
	Arjan van de Ven <arjan@...radead.org>,
	Franck Pommereau <pommereau@...v-paris12.fr>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

On Thursday 14 December 2006 15:37, Theodore Tso wrote:
> > +	  1 Gigabyte or more total physical RAM, answer "off" here.
>
> I don't think your proposed wording (1 gigabyte or more) versus (more
> than 1 gigabyte) doesn't really change the sense of this.

It does, because if you have exactly 1G of RAM, you should be using 
CONFIG_HIGHMEM, otherwise you will only be able to see ~896M.

This is >1G versus >=1G, the latter is clearly more correct.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ