linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>, Vitaliyi <imgrey@gmail.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata: add support for READ/WRITE LONG
Date: Tue, 13 Mar 2007 15:40:37 +0900	[thread overview]
Message-ID: <45F64765.10805@gmail.com> (raw)
In-Reply-To: <45F5A523.1080500@rtr.ca>

Mark Lord 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.
> 
> The fussy bit is that these commands require a non-standard
> sector size, usually 520 bytes instead of 512.
> 
> This patch adds support to libata for READ/WRITE LONG commands
> issued via SG_IO/ATA_16.
> 
> This patch was generated against a 2.6.21-rc3-git7 base:

I think it would be better if this comes in two patches.  One to add
qc->sect_size and convert all users of ATA_SECT_SIZE to qc->sect_size
and the other one to implement READ/WRITE LONG.  Another question is
whether this needs to be included into mainline.  This is definitely
useful but it is mostly for debugging/testing.

Hmmm... But we're gonna need qc->sect_size anyway for devices with
larger sector sizes and overhead for supporting READ/WRITE LONG is
nearly nill, so I'm voting for inclusion.

Thanks.

-- 
tejun

  parent reply	other threads:[~2007-03-13  6:40 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3aac340703102322p362998b9labedc13503702d2b@mail.gmail.com>
2007-03-12 14:47 ` libata extension Mark Lord
     [not found]   ` <3aac340703121003l43685599t8dbffe6247879a91@mail.gmail.com>
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
2007-03-13  0:08           ` Alan Cox
2007-03-12 23:40             ` Mark Lord
2007-03-13  6:40       ` Tejun Heo [this message]
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=45F64765.10805@gmail.com \
    --to=htejun@gmail.com \
    --cc=imgrey@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --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).