mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartosz SKOWRON <getxsick@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata - anomaly performance with NCQ
Date: Sat, 31 Jan 2009 02:25:11 +0100	[thread overview]
Message-ID: <77887e110901301725p64f5ab4fk341a9bfaf6715a7b@mail.gmail.com> (raw)
In-Reply-To: <4983A446.5080809@shaw.ca>

On Sat, Jan 31, 2009 at 2:07 AM, Robert Hancock <hancockr@shaw.ca> wrote:

>> 1) cause the title contains "with hdparm"...does it mean that
>> physically the performance is OK and only hdparm shows something
>> wrong?
> Well, hdparm is a fairly crude benchmark but there's likely at least some
> impact in other usage.

It's not an answer for my question. So, should I check with other
benchmarks? I thought that this's issue is investigated and the answer
is common. Do you recommend any "not crude" benchmarks? :)


>> 2) there is an information about upgrading firmware. as far as i know
>> Seagate doesn't publish firmwares. So the only way is to contact
>> seagate support, send the hdd and wait for the new one?
> I think Seagate can provide firmware updaters for the user to use, but
> normally only if you contact support I think.

I will send the email cause there is no phone line for my country.
BTW. upgrade firmware == damage data?

  reply	other threads:[~2009-01-31  1:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31  0:23 Bartosz SKOWRON
2009-01-31  1:07 ` Robert Hancock
2009-01-31  1:25   ` Bartosz SKOWRON [this message]
2009-01-31  5:18     ` Robert Hancock
2009-02-02  2:29       ` Bartosz SKOWRON

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=77887e110901301725p64f5ab4fk341a9bfaf6715a7b@mail.gmail.com \
    --to=getxsick@gmail.com \
    --cc=hancockr@shaw.ca \
    --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®