public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Hugh Dickins <hugh@veritas.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] rmap: parisc __flush_dcache_page
Date: 08 Apr 2004 10:47:23 -0500	[thread overview]
Message-ID: <1081439244.2165.236.camel@mulgrave> (raw)
In-Reply-To: <20040408153412.GD31667@dualathlon.random>

On Thu, 2004-04-08 at 10:34, Andrea Arcangeli wrote:
> yes, the spinlock in struct address_space would be enough, and that's
> what 2.4 does too, Andrew changed it to a semaphore in 2.6 but it can be
> made a spinlock again. Then you can fix it (as far as you never call it
> from an irq and as far as you don't generate exceptions inside the
> critical section, but I'm sure you don't).

Well, yes, of course we do.  We're a sofware tlb arch, so we generate
exceptions on tlb misses, which can occur anywhere (even in critical
sections).  However, the exceptions are carefully crafted not to take
spinlocks, so everything should be safe.

I'm not sure about the no in irq assertion.  The biggest use of
flush_dcache_page is on the I/O return path ... that looks like a good
candidate for being in interrupt (even though most drivers should be
offloading to softirq/tasklets).

James





  reply	other threads:[~2004-04-08 15:47 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 [this message]
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

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=1081439244.2165.236.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=andrea@suse.de \
    --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