From: Jens Axboe <axboe@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Dan Aloni <da-x@monatomic.org>, linux-kernel@vger.kernel.org
Subject: Re: Status of NCQ in libata
Date: Wed, 29 Mar 2006 09:15:38 +0200 [thread overview]
Message-ID: <20060329071538.GQ8186@suse.de> (raw)
In-Reply-To: <442A0980.6060403@gmail.com>
On Wed, Mar 29 2006, Tejun Heo wrote:
> Jens Axboe wrote:
> >On Sun, Mar 26 2006, Dan Aloni wrote:
> >>Hello,
> >>
> >>I'd like to know about the current status of NCQ support in libata,
> >>whether anyone is actively working on it, where I should find a
> >>development branch (there's no ncq branch anymore in libata-dev.git
> >>it seems) and when an upstream merge should be expected.
> >
> >You can give it a spin in the 'ncq' branch in the block layer git repo:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git
> >
> >Only one real bit needs to get merged in libata for ncq to be submitted,
> >and that is Tejun's eh rework. Once that is in, ncq becomes a fairly
> >small patch and can probably go straight in.
> >
> >AHCI is still the only supported controller, once NCQ is merged I'm sure
> >a few others will follow.
> >
>
> Patches going out later today. :) I've just ported the NCQ stuff over it
> and about to test it. As I have the doc and hardware NCQ support for
> sata_sil24 will soon follow.
Wonderful! I'm pretty confident in the NCQ stuff these days, so if Jeff
is up for it, it could make 2.6.17.
--
Jens Axboe
next prev parent reply other threads:[~2006-03-29 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 19:27 Status of NCQ in libata Dan Aloni
2006-03-27 7:29 ` Jens Axboe
2006-03-29 4:13 ` Tejun Heo
2006-03-29 7:15 ` Jens Axboe [this message]
2006-03-29 7:43 ` Dan Aloni
2006-03-29 7:46 ` Jens Axboe
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=20060329071538.GQ8186@suse.de \
--to=axboe@suse.de \
--cc=da-x@monatomic.org \
--cc=htejun@gmail.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