From: Jens Axboe <axboe@kernel.dk>
To: "Sam Bradshaw (sbradshaw)" <sbradshaw@micron.com>,
Christoph Hellwig <hch@infradead.org>,
"Asai Thambi Samymuthu Pattrayasamy (asamymuthupa)"
<asamymuthupa@micron.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mtip32xx blk-mq status?
Date: Wed, 26 Feb 2014 21:07:07 -0800 [thread overview]
Message-ID: <530EC7FB.3070204@kernel.dk> (raw)
In-Reply-To: <80B89753B40C5141A3E2D53FE7A2A8A982C86A74@NTXBOIMBX02.micron.com>
On 2014-02-26 20:42, Sam Bradshaw (sbradshaw) wrote:
>
>> On 2014-02-26 11:29, Christoph Hellwig wrote:
>>> Hi all,
>>>
>>> with blk-mq stabilizing in mainline and Jens using mtip32xx as tje
>> major
>>> example drivers in the past is there any progress on getting the
>>> conversion finished and merged?
>>
>> I'll pick up the pieces as soon as I get back and can test again. The
>> basic conversion is easy enough, I'll just dust that off. On top of
>> that
>> I started splitting the issue groups up, since it actually gets you a
>> good step further than just the basic conversion.
>
> If you have a public branch for the latter, send it our way. We can
> help with the SRSI testing.
Thanks, I'll get it setup next week.
>> The only problem area I ran into was the special case of the unaligned
>> writes.
>
> Yup, it's a painful limitation. If you need any p420m hardware, let me
> know.
Sure, a card for testing is always useful.
--
Jens Axboe
prev parent reply other threads:[~2014-02-27 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 19:29 mtip32xx blk-mq status? Christoph Hellwig
2014-02-26 19:40 ` Asai Thambi S P
2014-02-26 21:10 ` Jens Axboe
2014-02-27 4:42 ` Sam Bradshaw (sbradshaw)
2014-02-27 5:07 ` Jens Axboe [this message]
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=530EC7FB.3070204@kernel.dk \
--to=axboe@kernel.dk \
--cc=asamymuthupa@micron.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbradshaw@micron.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.