From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: bcrl@redhat.com, mingo@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] atomic pte updates and pae changes, take 2
Date: Sat, 14 Oct 2000 01:26:48 -0700 [thread overview]
Message-ID: <200010140826.BAA19023@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10010131841120.962-100000@penguin.transmeta.com> (message from Linus Torvalds on Fri, 13 Oct 2000 18:43:47 -0700 (PDT))
I dislike the "__HAVE_ARCH_xxx" approach, and considering that most
architectures will probably want to do something specific anyway I
wonder if we should get rid of that and just make architectures
have their own code.
Most software-based TLB refill systems could (and sparc64 will) make
all ref/mod bit updates occur in the kernel software fault path so
that none of this special synchronization is necessary.
In such cases it might be nice to have a generic version that all such
ports can share by just not defining __HAVE_ARCH_xxx.
Sure it's a bit ugly, but it does allow code sharing, so it probably
at least deserves a chance :-)
Later,
David S. Miller
davem@redhat.com
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-10-14 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-14 0:17 Ben LaHaise
2000-10-14 1:43 ` Linus Torvalds
2000-10-14 8:26 ` David S. Miller [this message]
2000-10-15 12:07 ` Ingo Molnar
2000-10-14 13:33 ` Stephen Tweedie
2000-10-15 12:01 ` Ingo Molnar
2000-10-19 20:16 ` oopses in test10-pre4 (was Re: [RFC] atomic pte updates and pae changes, take 3) Linus Torvalds
2000-10-20 5:44 ` Ben LaHaise
2000-10-20 17:18 ` Linus Torvalds
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=200010140826.BAA19023@pizda.ninka.net \
--to=davem@redhat.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=torvalds@transmeta.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