From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>, Vitaliyi <imgrey@gmail.com>,
Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata: add support for READ/WRITE LONG
Date: Mon, 12 Mar 2007 18:23:22 -0400 [thread overview]
Message-ID: <45F5D2DA.20407@rtr.ca> (raw)
In-Reply-To: <20070312221351.6c3db1fa@lxorguk.ukuu.org.uk>
Alan Cox wrote:
> On Mon, 12 Mar 2007 15:08:19 -0400
> Mark Lord <liml@rtr.ca> wrote:
>
>> The READ/WRITE LONG commands are theoretically obsolete,
>> but the majority of drives in existance still implement them.
>>
>> The WRITE_LONG and WRITE_LONG_ONCE commands are of particular
>> interest for fault injection testing -- eg. creating "media errors"
>> at specific locations on a disk.
>
> Do you still get hangs with ata_piix if you use R/W LONG and these
> changes ?
Err.. I *never* got hangs with ata_piix and these patches.
Either that, or the Alzheimer's is getting worse. ;)
???
next prev parent reply other threads:[~2007-03-12 22:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 7:22 libata extension Vitaliyi
2007-03-11 14:09 ` Bartlomiej Zolnierkiewicz
2007-03-12 14:47 ` Mark Lord
[not found] ` <3aac340703121003l43685599t8dbffe6247879a91@mail.gmail.com>
2007-03-12 17:12 ` Fwd: " Vitaliyi
2007-03-12 19:08 ` [PATCH] libata: add support for READ/WRITE LONG Mark Lord
2007-03-12 19:10 ` Mark Lord
2007-03-12 22:13 ` Alan Cox
2007-03-12 22:23 ` Mark Lord [this message]
2007-03-13 0:08 ` Alan Cox
2007-03-12 23:40 ` Mark Lord
2007-03-13 6:40 ` Tejun Heo
2007-03-13 10:46 ` Ric Wheeler
2007-03-16 12:28 ` Mark Lord
2007-03-16 14:02 ` Sergei Shtylyov
2007-03-16 14:22 ` Mark Lord
2007-03-16 14:33 ` Sergei Shtylyov
2007-03-16 14:42 ` Mark Lord
2007-03-16 14:43 ` Mark Lord
2007-03-16 14:58 ` Sergei Shtylyov
2007-03-16 15:07 ` Mark Lord
2007-03-16 15:23 ` Sergei Shtylyov
2007-03-16 15:32 ` Mark Lord
2007-03-16 17:08 ` Alan Cox
2007-03-16 18:54 ` Jeff Garzik
2007-03-16 20:16 ` Mark Lord
2007-03-16 20:38 ` Jeff Garzik
2007-03-16 21:05 ` Sergei Shtylyov
2007-03-16 21:09 ` Bartlomiej Zolnierkiewicz
2007-03-16 21:21 ` Mark Lord
2007-03-16 21:40 ` Bartlomiej Zolnierkiewicz
2007-04-04 6:20 ` Jeff Garzik
2007-03-16 15:15 ` Alan Cox
2007-03-16 14:16 ` Sergei Shtylyov
2007-03-16 15:01 ` Alan Cox
2007-03-16 14:15 ` Mark Lord
2007-03-16 14:23 ` Sergei Shtylyov
2007-03-16 14:33 ` Mark Lord
2007-03-16 15:23 ` Alan Cox
[not found] ` <3aac340703121007q35c7acf7t648e0ed7608be04d@mail.gmail.com>
[not found] ` <200703122106.39669.bzolnier@gmail.com>
2007-03-13 2:36 ` Fwd: libata extension Vitaliyi
2007-03-13 11:23 ` Jeff Garzik
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=45F5D2DA.20407@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=imgrey@gmail.com \
--cc=jgarzik@pobox.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 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.