mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Mismatch between hdaprm and sdparm output
Date: Mon, 07 Aug 2006 02:42:23 +0200	[thread overview]
Message-ID: <1154911344.3054.153.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <23691.1154910746@ocs3.ocs.com.au>

On Mon, 2006-08-07 at 10:32 +1000, Keith Owens wrote:
> NEC Versa S5200 laptop with FUJITSU MHV2080B SATA disk.  Kernel
> 2.6.16.21-0.13-smp (suselinux 10.1) using ata_piix.  hdparm and sdparm
> give inconsistent results, which one should I believe?  My main concern
> is write caching (XFS filesystem).

well write caching you should be able to benchmark easily.. does, say,
dbench or tiobench show any difference ?



      reply	other threads:[~2006-08-07  0:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07  0:32 Keith Owens
2006-08-07  0:42 ` Arjan van de Ven [this message]

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=1154911344.3054.153.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=kaos@ocs.com.au \
    --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

all inboxes | Powered by JetHome®