linux-kernel - Re: [PATCH v2] Introduce a version6 of autofs interface, to fix design error.

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: <4F9C6D4A.5080608@teksavvy.com>
Date:	Sat, 28 Apr 2012 18:20:58 -0400
From:	Mark Lord <kernel@...savvy.com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Michael Tokarev <mjt@....msk.ru>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux-kernel <linux-kernel@...r.kernel.org>,
	autofs@...r.kernel.org, Ian Kent <raven@...maw.net>,
	Thomas Meyer <thomas@...3r.de>, stable@...nel.org
Subject: Re: [PATCH v2] Introduce a version6 of autofs interface, to fix design
 error.

On 12-04-27 04:37 PM, H. Peter Anvin wrote:
> On 04/27/2012 08:47 AM, Mark Lord wrote:
>> On 12-04-27 05:45 AM, Michael Tokarev wrote:
>> ..
>>> Please note: the talk is about 32bit userspace on 64bit kernel,
>>> which should be quite rare these days, or something of less
>>> priority.
>>
>>
>> I suspect 32bit-PAE is more common than 32/64,
>> but both are valid and not uncommon in the wild.
> 
> 32-on-64 is a very important use case, because it lets us get people off
> 32-bit kernels.

Agreed.  But -PAE is even more important for the millions of people
with NVIDIA graphics controllers in their machines, or at least if
they want decent video playback.  :)

The otherwise-excellent NVIDIA drivers don't work in 32/64 mode,
but they do handle -PAE just fine.

Cheers
--
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/