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:	Sun, 19 Sep 2010 12:20:59 -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>,
	<linux@....linux.org.uk>
Subject: RE: [RFC][PATCH] Cross Memory Attach


(Adding Russell King of ARM Linux to CC list)

----------------------------------------
> From: torvalds@...ux-foundation.org
> Date: Thu, 16 Sep 2010 10:54:29 -0700
> Subject: Re: [RFC][PATCH] Cross Memory Attach
> To: peterz@...radead.org
> CC: cyeoh@....ibm.com; linux-kernel@...r.kernel.org
>
> On Thu, Sep 16, 2010 at 10:47 AM, Peter Zijlstra  wrote:
> > On Thu, 2010-09-16 at 10:34 -0700, Linus Torvalds wrote:
> >>
> >> 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().
> >
> > OK, fully agreed. Someone ought to tell ARM though :-)
>
> You know what? I don't care. If the fact that ARM is messing up means
> that they will never be able to do well in the micro-server space,
> that's _their_ problem.
>
> I fought HIGHMEM tooth and nail when it appeared originally. I lost,
> because we really didn't have any choice. But there is no way I'm
> going to say "oh, HIGHMEM still makes sense in 2010 because the ARM
> guys are now making all the same mistakes Intel did in 1992". Because
> these days we _do_ have a choice.
>
> And all the rumors are that there will be a 64-bit ARM too. So their
> PAE mess will be out before, but nobody sane should really consider it
> a primary issue. It will work, but it will work suboptimally. That's
> what you get when you have bad hardware design.
>
> Linus
> --
> 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/
>
>
 		 	   		  --
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