From: Jeremy Higdon <jeremy@sgi.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
akpm@osdl.org
Subject: Re: [PATCH] cdrom: longer timeout for "Read Track Info" command
Date: Tue, 2 Jan 2007 16:59:42 -0800 [thread overview]
Message-ID: <20070103005942.GB25765@sgi.com> (raw)
In-Reply-To: <20070102135052.GA2483@kernel.dk>
On Tue, Jan 02, 2007 at 02:50:53PM +0100, Jens Axboe wrote:
> Yep, I suspect this patch is long overdue. Jeremy, is this enough to fix
> it for you?
Yes, the 7 second timeout is fine. It actually takes about 6.7 seconds.
I guess if "another popular OS" has a 7 second timeout that we won't find
multimedia devices out there that take longer than that. :-)
My 15 seconds assumed that the observed case wasn't the worst case, but
it probably is.
This patch looks good.
Thanks
jeremy
> diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
> index 66d028d..3105ddd 100644
> --- a/drivers/cdrom/cdrom.c
> +++ b/drivers/cdrom/cdrom.c
> @@ -337,6 +337,12 @@ static const char *mrw_address_space[] = { "DMA", "GAA" };
> /* used in the audio ioctls */
> #define CHECKAUDIO if ((ret=check_for_audio_disc(cdi, cdo))) return ret
>
> +/*
> + * Another popular OS uses 7 seconds as the hard timeout for default
> + * commands, so it is a good choice for us as well.
> + */
> +#define CDROM_DEF_TIMEOUT (7 * HZ)
> +
> /* Not-exported routines. */
> static int open_for_data(struct cdrom_device_info * cdi);
> static int check_for_audio_disc(struct cdrom_device_info * cdi,
> @@ -1528,7 +1534,7 @@ void init_cdrom_command(struct packet_command *cgc, void *buf, int len,
> cgc->buffer = (char *) buf;
> cgc->buflen = len;
> cgc->data_direction = type;
> - cgc->timeout = 5*HZ;
> + cgc->timeout = CDROM_DEF_TIMEOUT;
> }
>
> /* DVD handling */
prev parent reply other threads:[~2007-01-03 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 2:36 [PATCH] cdrom: longer timeout for "Read Track Info" command Jeremy Higdon
2007-01-02 10:28 ` Alan
2007-01-02 13:50 ` Jens Axboe
2007-01-03 0:59 ` Jeremy Higdon [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=20070103005942.GB25765@sgi.com \
--to=jeremy@sgi.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).