public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI sg: Questions regarding jiffies usage
Date: Tue, 13 Jul 2004 01:59:39 +0200	[thread overview]
Message-ID: <20040712235939.GA4701@fs.tum.de> (raw)
In-Reply-To: <40F31ABA.1060709@torque.net>

On Mon, Jul 12, 2004 at 07:11:54PM -0400, Douglas Gilbert wrote:

> Adrian,

Hi Doug,

> There may be some confusion here. The older struct
> sg_header interface did not have explicit per command timeouts.
> As a poor substitute an ioctl was added to associate
> a timeout (in seconds) to the file descriptor. This way
> subsequent commands issued via that file descriptor
> got the new timeout value. This is the "sfp->timeout"
> value. The snippets above show the "sfp->timeout"
> value being set to a default when a sg device is opened
> and then being changed after a SG_SET_TIMEOUT ioctl call.
> 
> The newer sg_io_hdr interface has per command timeouts
> (in milliseconds). A sg_io_hdr::timeout value overrides
> the "sfp->timeout" value. In the above code the
> sg_io_hdr::timeout value is in "srp->header.timeout".

thanks for the explanations.

> Doug Gilbert

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2004-07-12 23:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-11  0:41 SCSI sg: Questions regarding jiffies usage Adrian Bunk
2004-07-12 19:35 ` Douglas Gilbert
2004-07-12 22:46   ` Adrian Bunk
2004-07-12 23:11     ` Douglas Gilbert
2004-07-12 23:59       ` Adrian Bunk [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=20040712235939.GA4701@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=dougg@torque.net \
    --cc=linux-scsi@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