From: Christoph Lameter <christoph@lameter.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH 0/7] abstract pagetable locking and pte updates
Date: Mon, 1 Nov 2004 16:19:31 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0411011616150.8399@server.graphe.net> (raw)
In-Reply-To: <4183009D.9080708@yahoo.com.au>
On Sat, 30 Oct 2004, Nick Piggin wrote:
> So it is a long way off from saying N architectures _do_ work,
> but the possibility is there.
There needs to be some fallback mechanism that allows to leave an arch the
way it is now and it will still work right. Then one can say that all
architectures will work.
> > What is unacceptable is the lack of research into the needs of arches
> > that has been put into this. The general core changes proposed can
> > never be adequate without a corresponding sweep of architecture-
> > specific code. While I fully endorse the concept of lockless pagetable
> > updates, there can be no correct implementation leaving architecture-
> > specific code unswept. I would encourage whoever cares to pursue this
> > to its logical conclusion to do the necessary reading, and audits, and
> > review of architecture manuals instead of designing core API's in vacuums.
> >
>
> Definitely - which is one of the reasons I posted it here, because I
> don't pretend to know all the arch details. But if you think I designed
> it in a vacuum you're wrong.
It is really a challenge to work with architectures that you cannot get
your hands on. We need to pool our resources otherwise this will never
work.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-11-02 0:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 7:20 Nick Piggin
2004-10-29 7:20 ` [PATCH 1/7] " Nick Piggin
2004-10-29 7:21 ` [PATCH 2/7] " Nick Piggin
2004-10-29 7:21 ` [PATCH 3/7] " Nick Piggin
2004-10-29 7:21 ` [PATCH 4/7] " Nick Piggin
2004-10-29 7:22 ` [PATCH 5/7] " Nick Piggin
2004-10-29 7:23 ` [PATCH 6/7] " Nick Piggin
2004-10-29 7:23 ` [PATCH 7/7] " Nick Piggin
2004-10-29 7:46 ` [PATCH 0/7] " William Lee Irwin III
2004-11-02 0:15 ` Christoph Lameter
2004-11-02 0:54 ` William Lee Irwin III
2004-11-02 1:34 ` Nick Piggin
2004-11-02 1:55 ` William Lee Irwin III
2004-11-02 2:38 ` Nick Piggin
2004-11-02 6:57 ` William Lee Irwin III
2004-11-02 17:55 ` Christoph Lameter
2004-10-29 11:45 ` Nick Piggin
2004-10-29 20:52 ` William Lee Irwin III
2004-10-30 2:46 ` Nick Piggin
2004-11-02 0:19 ` Christoph Lameter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0411011616150.8399@server.graphe.net \
--to=christoph@lameter.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=wli@holomorphy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox