From: "David S. Miller" <davem@redhat.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Mike Galbraith <mikeg@wen-online.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: kswapd deadlock 2.4.3-pre6
Date: Thu, 22 Mar 2001 02:02:40 -0800 (PST) [thread overview]
Message-ID: <15033.52672.923596.590263@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0103220411070.3306-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.31.0103212217320.10817-100000@penguin.transmeta.com> <Pine.LNX.4.21.0103220411070.3306-100000@freak.distro.conectiva>
Marcelo Tosatti writes:
> Are you sure flush_page_to_ram()/flush_icache_page() without
> page_table_lock held is ok for all archs?
This is actually a sticky area. For example, I remember that a long
time ago I noticed that it wasn't necessarily guarenteed that even
all the flush_tlb_{page,mm,range}() stuff was done under the page
table lock.
Maybe things have changed since then, but...
Furthermore I did not specify that flush_page_to_ram/flush_icache_page
can assume this, see Documentation/cachetlb.txt
I have no problem adding this invariant to some of the interfaces, but
we have to audit things.
> Looking at arch/mips/mm/r2300.c:
The r2300 port is UP-only btw...
Later,
David S. Miller
davem@redhat.com
prev parent reply other threads:[~2001-03-22 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 18:11 Mike Galbraith
2001-03-21 19:55 ` Rik van Riel
2001-03-21 20:05 ` Rik van Riel
2001-03-21 20:29 ` Linus Torvalds
2001-03-22 6:23 ` Linus Torvalds
2001-03-22 7:17 ` Marcelo Tosatti
2001-03-22 7:37 ` Mike Galbraith
2001-03-22 7:57 ` Mike Galbraith
2001-03-22 10:02 ` David S. Miller [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=15033.52672.923596.590263@pizda.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=riel@conectiva.com.br \
--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
all inboxes | Powered by JetHome®