All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	bzolnier@milosz.na.pl, Greg Stark <gsstark@mit.edu>,
	Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Todd Poynor <tpoynor@mvista.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	tim.bird@am.sony.com, dsingleton@mvista.com
Subject: Re: [PATCH] Configure IDE probe delays
Date: Wed, 01 Sep 2004 15:36:53 -0400	[thread overview]
Message-ID: <1094067412.1970.48.camel@krustophenia.net> (raw)
In-Reply-To: <4135EC84.6070407@rtr.ca>

On Wed, 2004-09-01 at 11:36, Mark Lord wrote:
> With good ADMA or host-queuing controllers that access system
> memory directly for their command blocks, then there's not much
> (if any) penalty for the extra LBA48 setup.  But for "normal"
> controllers (if such a beast even exists), the extra writes across
> the PCI bus can be costly.
> 
> Hardware write-buffer FIFOs between the CPU and the PCI bus
> can reduce the impact of this somewhat, but they are often
> only 2-4 entries deep, and will be filled by a normal (S)ATA
> command setup sequence.
> 
> This is one of those finer points that is very difficult to measure,
> since the I/O throughput is pretty much unaffected by it.  But CPU
> cycle count per-I/O setup is one way to measure it.
> 

The effect can be measured using a recent version of the voluntary
preemption patches, and disabling hardirq preemption.  In this situation
the IDE I/O completion is by far the longest non-preemptible code path,
so can be easily profiled from the latency traces.

Lee


  reply	other threads:[~2004-09-01 19:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 19:11 [PATCH] Configure IDE probe delays Todd Poynor
2004-07-30 21:36 ` Lee Revell
2004-07-30 22:35 ` Alan Cox
2004-07-31  0:12   ` Lee Revell
     [not found]     ` <200407311434.59604.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-31 18:00       ` Lee Revell
2004-08-27 17:45         ` Greg Stark
2004-08-27 17:53           ` Lee Revell
2004-08-27 18:05             ` Bartlomiej Zolnierkiewicz
2004-08-27 18:08               ` Lee Revell
2004-08-27 18:59                 ` Bartlomiej Zolnierkiewicz
2004-09-01 13:20                   ` Mark Lord
2004-09-01 14:43                     ` Jeff Garzik
2004-09-01 15:30                       ` Mark Lord
2004-09-01 15:36                       ` Mark Lord
2004-09-01 19:36                         ` Lee Revell [this message]
2004-09-01 18:42                           ` Alan Cox
2004-09-01 15:06                     ` Alan Cox
2004-09-01 19:08                       ` Lee Revell
2004-09-02 16:04                       ` Mark Lord
2004-09-01 15:40                     ` Bartlomiej Zolnierkiewicz
2004-07-31 18:06       ` Lee Revell
2004-07-31 19:35         ` Alan Cox
2004-07-31 21:35           ` Lee Revell
2004-07-31 21:44             ` Jeff Garzik
2004-07-31 22:12               ` Lee Revell
2004-08-04 17:30               ` Anthony de Boer
2004-08-05 21:39           ` Tim Bird
2004-07-31  0:54   ` Jeff Garzik
2004-08-03 17:47     ` Mark Lord
2004-08-06 15:48       ` Jeff Garzik
2004-08-06 19:29         ` Tim Bird
2004-08-06 20:46           ` Todd Poynor
2004-08-02 21:56   ` Tim Bird
2004-08-02 21:01     ` Alan Cox

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=1094067412.1970.48.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@milosz.na.pl \
    --cc=dsingleton@mvista.com \
    --cc=gsstark@mit.edu \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=tim.bird@am.sony.com \
    --cc=tpoynor@mvista.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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.