public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Bob Tracy <rct@gherkin.frus.com>, Kurt Garloff <garloff@suse.de>,
	Linux SCSI list <linux-scsi@vger.kernel.org>,
	Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Format Unit can take many hours
Date: Tue, 11 May 2004 20:30:13 +0200	[thread overview]
Message-ID: <20040511183013.GC14789@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.33.0405111243300.14297-100000@sweetums.bluetronic.net>

On Tue, May 11 2004, Ricky Beam wrote:
> On Tue, 11 May 2004, Bob Tracy wrote:
> >Moreover, it simply "feels" wrong to define a constant for something
> >that isn't...  The quick fix of increasing the timeout doesn't address
> >the underlying issue of how long a format should take, and as Ricky
> >implies, that's probably more the concern of the application rather
> >than the driver.
> 
> The real problem is a lack of being able to specify a timeout for user
> supplied commands.  In-kernel drivers can set a command timeout.  The
> IOCTL interface does not export that capability.

Noone should use that interface, period. That ioctl is about as bad an
interface as you could imagine. Use any variant of sg and you should be
fine.

-- 
Jens Axboe


      reply	other threads:[~2004-05-11 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 11:49 [PATCH] Format Unit can take many hours Kurt Garloff
2004-05-11 12:20 ` Jens Axboe
2004-05-11 12:40   ` Arjan van de Ven
2004-05-11 12:46     ` Jens Axboe
2004-05-11 12:44   ` Kurt Garloff
2004-05-11 16:10   ` Jeff Garzik
2004-05-11 16:14     ` Jens Axboe
2004-05-11 16:26       ` Kurt Garloff
2004-05-11 17:27         ` Jens Axboe
2004-05-11 14:01 ` Ricky Beam
2004-05-11 16:28   ` Bob Tracy
2004-05-11 16:44     ` Ricky Beam
2004-05-11 18:30       ` Jens Axboe [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=20040511183013.GC14789@suse.de \
    --to=axboe@suse.de \
    --cc=garloff@suse.de \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rct@gherkin.frus.com \
    /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