All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Wilcox <Matthew.Wilcox@genedata.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Dino PCI and I/O spaces
Date: Mon, 14 Jun 1999 17:37:57 +0200	[thread overview]
Message-ID: <19990614173757.L31472@mencheca.ch.genedata.com> (raw)
In-Reply-To: <E10tYYE-00067e-00@the-village.bc.nu>; from Alan Cox on Mon, Jun 14, 1999 at 04:21:29PM +0100

On Mon, Jun 14, 1999 at 04:21:29PM +0100, Alan Cox wrote:
> > On Mon, Jun 14, 1999 at 04:15:08PM +0100, Alan Cox wrote:
> > > Also as a btw: PCI I/O port access will suck rocks on HP because we have
> > > to grab a lock since it is a two stage operation. That may mean we want
> > > to write smart copy/csum/io and ins* functions for PCI block I/O.
> > 
> > Do we only have to grab a lock on SMP machines, or can we sleep between
> > the two accesses?
> 
> On a uniprocessor we might take an interrupt between the two cycles. So we
> have to suffer anyway

Then we ought to disable interrupts, surely?  Otherwise we can have:

Grab lock
interrupt taken
driver attempts to perform IO, tries to take lock, machine hangs solid.

Or what sort of locking scheme did you have in mind?

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

  reply	other threads:[~1999-06-14 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-14 15:15 [parisc-linux] Dino PCI and I/O spaces Alan Cox
1999-06-14 15:21 ` Matthew Wilcox
1999-06-14 15:21   ` Alan Cox
1999-06-14 15:37     ` Matthew Wilcox [this message]
1999-06-14 16:10       ` Alan Cox
1999-06-14 20:15 ` Grant Grundler
1999-06-14 23:05   ` Alan Cox
1999-06-15  0:48     ` Grant Grundler

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=19990614173757.L31472@mencheca.ch.genedata.com \
    --to=matthew.wilcox@genedata.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.