[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=hFydeqk_ENGmqEqwqduSeN2gpjMr+VpcN38Xx@mail.gmail.com>
Date: Thu, 16 Sep 2010 10:54:29 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Christopher Yeoh <cyeoh@....ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] Cross Memory Attach
On Thu, Sep 16, 2010 at 10:47 AM, Peter Zijlstra <peterz@...radead.org> 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/
Powered by blists - more mailing lists