From: Andrea Arcangeli <andrea@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] rmap: parisc __flush_dcache_page
Date: Thu, 8 Apr 2004 18:13:22 +0200 [thread overview]
Message-ID: <20040408161322.GE31667@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0404081626460.7248-100000@localhost.localdomain>
On Thu, Apr 08, 2004 at 04:35:12PM +0100, Hugh Dickins wrote:
> It's not fixable via the i_shared_sem, but we can add another layer
I meant it's unfixable unless we change the VM common code.
> of spin_lock around the i_mmap* list/tree manipulations, one that
> preprocesses away to nothing on all arches but parisc and arm, and
> is used in their __flush_dcache_page. *Not* the page_table_lock ;)
I'd prefer to use only a spinlock then to carry around two overlapping
locks, the need_resched() check is needed anyways even with preempt in
the real costly paths.
prev parent reply other threads:[~2004-04-08 16:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 13:41 rmap: parisc __flush_dcache_page Hugh Dickins
2004-04-08 13:52 ` [parisc-linux] " James Bottomley
2004-04-08 14:16 ` Hugh Dickins
2004-04-08 14:40 ` James Bottomley
2004-04-08 15:14 ` Andrea Arcangeli
2004-04-08 15:28 ` James Bottomley
2004-04-08 15:34 ` Andrea Arcangeli
2004-04-08 15:47 ` James Bottomley
2004-04-08 16:16 ` Andrea Arcangeli
2004-04-08 16:29 ` James Bottomley
2004-04-08 17:10 ` Andrea Arcangeli
2004-04-08 17:43 ` James Bottomley
2004-04-08 17:51 ` Andrea Arcangeli
2004-04-08 18:07 ` James Bottomley
2004-04-08 18:18 ` Andrea Arcangeli
2004-04-08 18:28 ` James Bottomley
2004-04-08 18:42 ` Andrea Arcangeli
2004-04-08 18:49 ` James Bottomley
2004-04-08 19:02 ` Andrea Arcangeli
2004-04-10 1:21 ` Paul E. McKenney
2004-04-08 15:35 ` Hugh Dickins
2004-04-08 16:13 ` Andrea Arcangeli [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=20040408161322.GE31667@dualathlon.random \
--to=andrea@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@parisc-linux.org \
/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