mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: Andre Hedrick <andre@linux-ide.org>, linux-kernel@vger.kernel.org
Subject: Re: readsw/writesw readsl/writesl
Date: 27 Aug 2002 18:25:24 +0100	[thread overview]
Message-ID: <1030469124.5695.9.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020827.003027.26962443.davem@redhat.com>

On Tue, 2002-08-27 at 08:30, David S. Miller wrote:
> The only reason insl() exists is because the x86 has special
> instructions to perform that operation.
> 
> It used to be an optimization when cpus were really slow.

readsl becomes relevant once people start shipping bridges that can do
asynchronous pci mmio read or burst mode to order however

I wonder if thats something we should plan for now ?


  parent reply	other threads:[~2002-08-27 17:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 20:52 [BKPATCH] Read-Copy Update 2.5 Dipankar Sarma
2002-08-27  0:24 ` Rusty Russell
2002-08-27  6:11   ` Dipankar Sarma
2002-08-27  6:11     ` David S. Miller
2002-08-27  6:23       ` readsw/writesw readsl/writesl Andre Hedrick
2002-08-27  6:43         ` David S. Miller
2002-08-27  6:55           ` Andre Hedrick
2002-08-27  7:30         ` David S. Miller
2002-08-27  6:46           ` Benjamin Herrenschmidt
2002-08-27  6:49             ` Benjamin Herrenschmidt
2002-08-27 17:25           ` Alan Cox [this message]
2002-08-27 21:31             ` David S. Miller
2002-08-27 13:58       ` [BKPATCH] Read-Copy Update 2.5 Dipankar Sarma
2002-08-27 16:00 readsw/writesw readsl/writesl Richard.Zidlicky
2002-08-27  9:29 ` Benjamin Herrenschmidt
2002-08-28 12:23   ` Richard Zidlicky
2002-08-28 16:17     ` Benjamin Herrenschmidt
2002-08-29  9:17       ` Richard Zidlicky

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=1030469124.5695.9.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®