From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@redhat.com>,
torvalds@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
axboe@suse.dk
Subject: Re: Nasty IDE crasher in 2.6.9rc1
Date: Fri, 3 Sep 2004 17:19:28 +0200 [thread overview]
Message-ID: <20040903151928.GE1717@suse.de> (raw)
In-Reply-To: <1094219998.7975.4.camel@localhost.localdomain>
On Fri, Sep 03 2004, Alan Cox wrote:
> On Gwe, 2004-09-03 at 15:50, Jens Axboe wrote:
> > (suse.dk is not related to suse.de and it helpfully eats all messages
> > sent to unknown users. not so great :(
>
> Ah sorry.
>
> > > Another problem with barrier is that it can take several minutes worst case
> > > for the command to complete on a large modern drive (timings c/o friendly
> > > ide drive engineer). That causes two problems I've pointed out to Jens that
> > > we need to fix before barriers are IMHO production grade
> >
> > Can you pass me his results?
>
> I can ask. Its NDA data (not Maxtor). Or Eric might have public info ?
> The later mail I reported my tests trying to make it as slow as possible
> and I couldn't get worse than 7 seconds for the command.
IIRC, 7 seconds is the magic number that Microsoft uses for when a
command times out in the kernel... That might make the results a little
suspicious :)
>
> > > 2. The timeouts on the command issue appear to be too small, and
> > > we will time out and reset the drive in loaded situations.
> >
> > You don't seem to address that in your patch?
>
> I'm not sure what the right answer is.
I guess as a first measure just increasing the timeout two-fold will
cover most of the problem.
--
Jens Axboe
prev parent reply other threads:[~2004-09-03 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 14:23 Nasty IDE crasher in 2.6.9rc1 Alan Cox
2004-09-03 14:50 ` Jens Axboe
2004-09-03 13:59 ` Alan Cox
2004-09-03 15:19 ` 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=20040903151928.GE1717@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=axboe@suse.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.