From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>, Jonathan Corbet <corbet@lwn.net>,
Boaz Harrosh <bharrosh@panasas.com>,
Zach Brown <zach.brown@oracle.com>,
Chris Mason <chris.mason@oracle.com>, Tejun Heo <tj@kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: LSF Papers online?
Date: Tue, 14 Apr 2009 23:58:26 -0400 [thread overview]
Message-ID: <1239767906.15559.1.camel@mulgrave> (raw)
In-Reply-To: <49E53AE6.4010803@gmail.com>
On Tue, 2009-04-14 at 19:39 -0600, Robert Hancock wrote:
> James Bottomley wrote:
> >
> > On a final note about the urgency of getting libata out of SCSI: Intel
> > has been worrying for a while about the fatness of the SCSI/libata
> > stack, and its effects on performance, especially command transmission
> > via SAT, so I'm hoping they'll be supporting the effort.
>
> I really don't see this as being a big driver for this move. If you look
> at the code that does the translation of SCSI commands to ATA commands,
> there really is not much there at all of any consequence to CPU usage.
> Compared to any kind of hardware/controller interactions I wouldn't say
> it's likely to be a significant bottleneck at all. In oprofile runs I've
> done with heavy ATA activity, the top time consumers are the interrupt
> handlers, command issue paths, code that actually is poking IO
> registers. The libata-scsi code hasn't even shown up on the radar in my
> experience.
Been there, said that and got the nicely embroidered polo shirt to prove
it.
The point is, it doesn't really matter what I say or believe, it matters
what they do ... and they believe fat stacks impede the performance of
their SSDs.
James
next prev parent reply other threads:[~2009-04-15 3:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 12:53 LSF Papers online? Boaz Harrosh
2009-04-13 13:58 ` James Bottomley
2009-04-13 14:42 ` Boaz Harrosh
2009-04-13 14:51 ` James Bottomley
2009-04-13 15:19 ` Chris Mason
2009-04-13 15:44 ` Boaz Harrosh
2009-04-13 16:45 ` Theodore Tso
2009-04-13 18:11 ` Jonathan Corbet
2009-04-13 20:05 ` Nicholas A. Bellinger
2009-04-13 21:40 ` Bartlomiej Zolnierkiewicz
2009-04-13 21:49 ` Bartlomiej Zolnierkiewicz
2009-04-13 22:24 ` Jeff Garzik
2009-04-14 1:24 ` Bartlomiej Zolnierkiewicz
2009-04-14 10:14 ` Jeff Garzik
2009-04-14 14:54 ` Bartlomiej Zolnierkiewicz
2009-04-14 15:40 ` Jeff Garzik
2009-04-14 16:54 ` Alan Cox
2009-04-14 22:09 ` Bartlomiej Zolnierkiewicz
2009-04-14 22:49 ` James Bottomley
2009-04-15 1:39 ` Robert Hancock
2009-04-15 3:58 ` James Bottomley [this message]
2009-04-15 8:30 ` Alan Cox
2009-04-16 6:31 ` Grant Grundler
2009-04-16 16:37 ` James Bottomley
2009-04-16 17:45 ` Matthew Wilcox
2009-04-14 23:14 ` Jeff Garzik
2009-04-15 9:28 ` Alan Cox
2009-04-15 13:38 ` Bartlomiej Zolnierkiewicz
2009-04-15 14:56 ` Alan Cox
2009-04-16 16:01 ` Bartlomiej Zolnierkiewicz
2009-04-14 3:30 ` Tejun Heo
2009-04-14 14:47 ` Bartlomiej Zolnierkiewicz
2009-04-16 21:36 ` Grant Grundler
2009-04-17 4:44 ` Martin K. Petersen
2009-04-18 4:06 ` Grant Grundler
2009-04-19 11:00 ` Boaz Harrosh
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=1239767906.15559.1.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bharrosh@panasas.com \
--cc=bzolnier@gmail.com \
--cc=chris.mason@oracle.com \
--cc=corbet@lwn.net \
--cc=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@kernel.org \
--cc=zach.brown@oracle.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.