All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	Rene Herman <rene.herman@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.20-rc2+: CFQ halving disk throughput.
Date: Wed, 03 Jan 2007 02:53:52 +0900	[thread overview]
Message-ID: <459A9C30.20204@gmail.com> (raw)
In-Reply-To: <459A97EC.8090903@rtr.ca>

Mark Lord wrote:
> Tejun Heo wrote:
>>
>> OT but care to make -i and -I work equivalently?  Such that -i reports
>> more detailed info and user can dump stored id block.
> 
> hdparm -I works just fine now.

No objection there.

> hdparm -i requires the HDIO_GET_IDENTITY ioctl() from drivers/ide,
> to retrieve the "boot time" copy of the identify block, before any
> mods are made by the driver.  But in recent years, drivers/ide has
> broken it, in that it tries to maintain the "boot time" copy in sync
> with the on-drive copy.  Kinda makes -i pointless.
> 
> Is there a way to retrieve the libata cached copy of the ID block?
> How?

Just implemented and posted patch for HDIO_GET_IDENTITY in an attempt to
access ATAPI IDENTIFY block using hdparm.

>> Support for IDENTIFY PACKET DEVICE would be nice too.
> 
> It already does that, using HDIO_DRIVE_CMD to retrieve it
> in the same way as for regular IDENTIFY DEVICE commands.

Hmmm... My hdparm doesn't seem to do that.

# hdparm -V
hdparm v6.9
# hdparm -I /dev/sr0

/dev/sr0:
 HDIO_DRIVE_CMD(identify) failed: Input/output error

Am I missing something?

> In hdparm-7.0, I'll have it use ATA passthrough when possible
> for most/all commands.

Glad to hear.

Happy new year.

-- 
tejun

  reply	other threads:[~2007-01-02 17:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 13:37 PATA -- pata_amd on 2.6.19 fails to IDENTIFY my DVD-ROM Rene Herman
2006-12-27  7:19 ` Tejun Heo
2006-12-27 17:50   ` Rene Herman
2006-12-28  2:24     ` Tejun Heo
2007-01-01 22:46       ` 2.6.20-rc2+: CFQ halving disk throughput Rene Herman
2007-01-01 22:56         ` Rene Herman
2007-01-01 23:30           ` Linus Torvalds
2007-01-01 23:28         ` Mark Lord
2007-01-02  8:34           ` Jens Axboe
2007-01-02 15:01             ` Mark Lord
2007-01-02 16:53               ` Tejun Heo
2007-01-02 17:35                 ` Mark Lord
2007-01-02 17:53                   ` Tejun Heo [this message]
2007-01-02 18:10                     ` Mark Lord
2007-01-02 21:50                     ` ATA_12 support for libata/ATAPI devices Mark Lord
2007-01-02 17:09               ` 2.6.20-rc2+: CFQ halving disk throughput Jan Engelhardt
2007-01-02  5:36         ` Andrew Morton
2007-01-02  8:44           ` Jens Axboe
2007-01-02 10:24             ` Rene Herman
2007-01-02 11:57               ` Jens Axboe
2007-01-02 12:10                 ` Jens Axboe
2007-01-02 15:12                   ` Mark Lord
2007-01-02 15:14                     ` Jens Axboe
2007-01-02 15:40                       ` Mark Lord
2007-01-02 15:45                         ` 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=459A9C30.20204@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=rene.herman@gmail.com \
    --cc=torvalds@osdl.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.