linux-kernel - RE: [RFC][PATCH] Cross Memory Attach

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]

Date:	Sat, 18 Sep 2010 21:55:30 -0700
From:	Yuhong Bao <yuhongbao_386@...mail.com>
To:	<torvalds@...ux-foundation.org>, <peterz@...radead.org>
CC:	<cyeoh@....ibm.com>, <linux-kernel@...r.kernel.org>
Subject: RE: [RFC][PATCH] Cross Memory Attach


> Of course, these days I would seriously suggest against trying to
> optimize the kmap() case. It only matters on crap hardware these days.
> Anybody running HIGHMEM in 2010 and thinks that it makes sense
> deserves the pain the get. We should not complicate the kernel further
> for it, and sane architectures will have a no-op kmap().

Well, keep in mind most even vaguely recent 32-bit x86 distro kernels
have HIGHMEM4G enabled by default.
Some recent ones even have HIGHMEM64G enabled in order to get NX support.
(And yes, as I said before, there are many processors that cannot run in long mode
but have NX)

Yuhong Bao
 		 	   		  --
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/