linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zoltan Boszormenyi <zboszor@dunaweb.hu>
To: Jeff Garzik <jeff@garzik.org>
Cc: akpm@linux-foundation.org, kluo@nvidia.com, pchen@nvidia.com,
	Robert Hancock <hancockr@shaw.ca>,
	linux-ide@vger.kernel.org
Subject: Re: [patch 05/25] ata: add the SW NCQ support to sata_nv for MCP51/MCP55/MCP61
Date: Wed, 26 Sep 2007 07:46:11 +0200	[thread overview]
Message-ID: <46F9F223.4000406@dunaweb.hu> (raw)
In-Reply-To: <46F9F05F.40905@garzik.org>

Jeff Garzik írta:
> Zoltan Boszormenyi wrote:
>> Jeff Garzik írta:
>>> Zoltan Boszormenyi wrote:
>>>> Hi,
>>>>
>>>> Jeff Garzik írta:
>>>>> akpm@linux-foundation.org wrote:
>>>>>> From: Kuan Luo <kluo@nvidia.com>
>>>>>>
>>>>>> Add the Software NCQ support to sata_nv.c for MCP51/MCP55/MCP61 SATA
>>>>>> controller.  NCQ function is disable by default, you can enable 
>>>>>> it with
>>>>>> 'swncq=1'.  NCQ will be turned off if the drive is Maxtor on 
>>>>>> MCP51 or MCP55
>>>>>> rev 0xa2 platform.
>>>>>>
>>>>>> [akpm@linux-foundation.org: build fix]
>>>>>> Signed-off-by: Kuan Luo <kluo@nvidia.com>
>>>>>> Signed-off-by: Peer Chen <pchen@nvidia.com>
>>>>>> Cc: Zoltan Boszormenyi <zboszor@dunaweb.hu>
>>>>>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>>>>>> ---
>>>>>>
>>>>>>  drivers/ata/sata_nv.c |  860 
>>>>>> +++++++++++++++++++++++++++++++++++++++-
>>>>>>  1 files changed, 851 insertions(+), 9 deletions(-)
>>>>>
>>>>> I finally gave this a thorough review.
>>>>>
>>>>> Overall, good work.  The state transitions all seem solid.  I made 
>>>>> several minor changes and cleanups, and checked it into the 
>>>>> 'nv-swncq' branch of 
>>>>> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>>>>>
>>>>> Two hurdles before I'm ready to push upstream:
>>>>>
>>>>> * someone please verify my minor changes did not break anything; I 
>>>>> don't have real hardware
>>>>
>>>> After reading the diff between the original and your cleaned up 
>>>> version
>>>> it seems both the change from 4 individual flags to a single 
>>>> integer and the
>>>> nv_swncq_bmdma_stop() -> __ata_bmdma_stop() transition are 
>>>> obviously correct.
>>>> I attached a small cleanup patch which may make one check a bit 
>>>> more readable.
>>>>
>>>> However, can you explain this chunk below? Why isn't it needed?
>>>>
>>>> @@ -615,7 +622,6 @@ static const struct ata_port_info nv_por
>>>>        {
>>>>                .sht            = &nv_swncq_sht,
>>>>                .flags          = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY,
>>>> -               .link_flags     = ATA_LFLAG_HRST_TO_RESUME,
>>>>                .pio_mask       = NV_PIO_MASK,
>>>>                .mwdma_mask     = NV_MWDMA_MASK,
>>>>                .udma_mask      = NV_UDMA_MASK,
>>>
>>> that's a bug.  fixed.
>>>
>>> I also applied your cleanup.
>>
>> Thanks, but you took the wrong cleanup patch.
>> My original, i.e. this chunk below is wrong.
>>
>> @@ -2291,8 
>> <http://git.kernel.org/?p=linux/kernel/git/jgarzik/libata-dev.git;a=blob;f=drivers/ata/sata_nv.c;h=540f218e10e56c8a85a937bc920a5d96434bcc8f;hb=41f0f8af3edfccd58b5c9d714928d773a072b693#l2291> 
>> +2283,7 
>> <http://git.kernel.org/?p=linux/kernel/git/jgarzik/libata-dev.git;a=blob;f=drivers/ata/sata_nv.c;h=ffd00f5c533d7b58dde67cfef7d2191ca15ea140;hb=5a5a9e1890b8260686218a68862d880daee1a817#l2283> 
>> @@ static void nv_swncq_host_interrupt(struct ata_port *ap, u16 fis)
>>                 */
>>                pp->dhfis_bits |= (0x1 << pp->last_issue_tag);
>>                pp->ncq_flags |= ncq_saw_d2h;
>> -               if ((pp->ncq_flags & ncq_saw_sdb) ||
>> -                   (pp->ncq_flags & ncq_saw_backout)) {
>> +               if (pp->ncq_flags & (ncq_saw_sdb || ncq_saw_backout)) {
>>                        ata_ehi_push_desc(ehi, "illegal fis 
>> transaction");
>>                        ehi->err_mask |= AC_ERR_HSM;
>>                        ehi->action |= ATA_EH_HARDRESET;
>>
>> It should be a binary OR between the flags. This caused immediate
>> NCQ errors upon boot and lead to disabling NCQ.
>> My second patch has it corrected.
>
> fixed

Thanks. And would you please also enable swncq by default? :-)
It's very stable.

Best regards,
Zoltán Böszörményi



  reply	other threads:[~2007-09-26  5:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 20:59 [patch 05/25] ata: add the SW NCQ support to sata_nv for MCP51/MCP55/MCP61 akpm
2007-09-20 22:40 ` Jeff Garzik
2007-09-21  5:54   ` Zoltan Boszormenyi
2007-09-21  8:04     ` Zoltan Boszormenyi
2007-09-26  3:48     ` Jeff Garzik
2007-09-26  5:36       ` Zoltan Boszormenyi
2007-09-26  5:38         ` Jeff Garzik
2007-09-26  5:46           ` Zoltan Boszormenyi [this message]
2007-09-27  6:12             ` Kuan Luo
2007-09-27  6:19               ` Jeff Garzik
2007-09-27  6:56                 ` Kuan Luo
2007-09-27  7:10                   ` Jeff Garzik
2007-09-27  7:33                     ` Kuan Luo
2007-09-27  8:54                     ` Kuan Luo
2007-10-04  6:31                       ` Peer Chen
2007-10-12 21:15                       ` Jeff Garzik
2007-10-14 12:29                         ` Kuan Luo

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=46F9F223.4000406@dunaweb.hu \
    --to=zboszor@dunaweb.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hancockr@shaw.ca \
    --cc=jeff@garzik.org \
    --cc=kluo@nvidia.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=pchen@nvidia.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 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).