linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Sloan <russell.sloan@lingua-data.com>
To: htejun@gmail.com
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA timeout value
Date: Mon, 23 Apr 2007 11:11:54 -0400	[thread overview]
Message-ID: <14380803.14661177341114878.JavaMail.servlet@perfora> (raw)

I'm using SG_IO and I'm curently passing in:
  sg_io_hdr_t.timeout = 5;

This should be a 5 ms timeout, correct?  I've tried a few different values, from 5 to 1000 and it still takes 90+ seconds for it to timeout and return to my program.

I will try HDIO and see if that behaves any differently.



Russell Sloan wrote:
> Hi everyone,
> 
> Can someone point me to the area in the SATA code that is responsible
> for timing out while checking on a drive connection?
> 
> I have a drive that shuts its SATA interface down while it is doing a
> Security Erase, and then powers back up when it's done.  When I poll
> the drive asking for its status during the Erase, it is "not there"
> but the driver takes quite a while to report back.  I'd like to
> reduce the time that the driver spends checking for the drive.

What tool do you use to issue the query?  If the program uses SG_IO, the
timeout is specified by the program.  If it uses something else (one of
HDIO ioctls), timeouts are hardcoded in the ioctl functions in
libata-scsi.c - currently 10secs.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2007-04-23 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 15:11 Russell Sloan [this message]
2007-04-23 15:50 ` SATA timeout value Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2007-04-23 16:46 Russell Sloan
2007-04-23 22:07 ` Mark Lord
2007-04-24  8:25 ` Tejun Heo
2007-04-21 23:24 Russell Sloan
2007-04-23  6:59 ` Tejun Heo

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=14380803.14661177341114878.JavaMail.servlet@perfora \
    --to=russell.sloan@lingua-data.com \
    --cc=htejun@gmail.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 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).