From: Jeff Moyer <jmoyer@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]"
<asamymuthupa@micron.com>,
linux-ide@vger.kernel.org
Subject: Re: New driver mtipx2xx submission
Date: Mon, 02 May 2011 14:40:09 -0400 [thread overview]
Message-ID: <x49oc3lndyu.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20110428230605.78c55c70@lxorguk.ukuu.org.uk> (Alan Cox's message of "Thu, 28 Apr 2011 23:06:05 +0100")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> We have written a new block driver for our AHCI based PCIe SSDs. The
>> main objective of our product is providing high performance. Traffic
>> through OS storage stack is not to able fully utilize the device's
>> capabilty. To improve the traffic to the device and hence
>> showcase/utilize the device's capability, we have come up with this new
>> block driver. This driver includes
>> * utilize device's increased queue depth
>> * workaround for hardware errata
>>
>> We want to get this driver into kernel tree to support the device out of
>> the box. Attached this driver as a patch for latest kernel. We would
>> like to get your comments, and also open for discussion.
>
> The kernel starting point would be that we have an AHCI driver. If you
> need workarounds for hardware errata then they can go into it and that is
> fine. We support NCQ so we can use the queue depths. If there are
> extensions then the AHCI driver can be enhanced.
Given the highly parallel nature of these parts, I wouldn't be surprised
if the ahci queue depth of 31 is one of the main bottlenecks. Can you
think of a way to extend the ahci driver in this manner to accommodate
devices like this one?
Cheers,
Jeff
next prev parent reply other threads:[~2011-05-02 18:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 15:53 New driver mtipx2xx submission Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-04-28 22:06 ` Alan Cox
2011-05-02 12:40 ` Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-05-02 17:42 ` Alan Cox
2011-05-03 20:07 ` [PATCH 0/3] " Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-05-11 17:40 ` Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-05-11 19:20 ` Alan Cox
2011-05-21 2:26 ` Asai Thambi S P
2011-05-25 14:36 ` Jeff Moyer
[not found] ` <22A973199D2C2F46933448F6E7990A300239EA77@ntxboimbx31.micron.com>
2011-06-01 19:51 ` Jeff Moyer
2011-06-01 20:21 ` Alan Cox
2011-06-15 1:29 ` Asai Thambi S P
2011-06-15 14:43 ` Jeff Moyer
2011-06-27 23:38 ` Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-06-28 15:18 ` Jeff Moyer
2011-06-28 15:31 ` Alan Cox
2011-06-28 15:38 ` Jeff Moyer
2011-07-06 21:43 ` Asai Thambi S P
2011-07-07 7:37 ` Alan Cox
2011-07-26 10:46 ` Alan Cox
2011-07-26 11:44 ` Christoph Hellwig
2011-07-26 11:49 ` Alan Cox
2011-07-26 18:50 ` Jeff Garzik
2011-07-29 18:13 ` Asai Thambi S P
2011-08-11 18:36 ` Asai Thambi S P
2011-07-06 21:39 ` Asai Thambi S P
2011-06-02 1:21 ` David Dillow
2011-06-15 1:33 ` Asai Thambi S P
2011-06-15 3:12 ` David Dillow
2011-05-02 18:40 ` Jeff Moyer [this message]
2011-05-02 18:52 ` Alan Cox
2011-05-03 15:04 ` Mark Lord
2011-05-03 15:07 ` Alan Cox
2011-05-03 15:08 ` Mark Lord
2011-05-03 15:02 ` Mark Lord
2011-05-12 14:39 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2011-05-03 11:09 Jordan_Hargrave
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=x49oc3lndyu.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=asamymuthupa@micron.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).