All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Jamie Clark <jamie@metaparadigm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23pre6aa3 scsi oops
Date: Sat, 6 Dec 2003 02:05:05 +0100	[thread overview]
Message-ID: <20031206010505.GB14904@dualathlon.random> (raw)
In-Reply-To: <3FA79308.3070300@metaparadigm.com>

On Tue, Nov 04, 2003 at 07:52:40PM +0800, Jamie Clark wrote:
> I made the quick fix (disabling rq_mergeable) and started the load test.
> Will let it run for a week or so.

does your later recent email means it deadlocked again even with this
disabled?

Could you try again with 2.4.23aa1 again just in case?

> FYI an observation from my last test: the read latency seems to be much
> improved and more consistent under this kernel (2.4.23pre6aa3, before
> the oops and before this fix).  The maximum latency seemed steady over
> the whole test without any of the longish pauses that showed up under
> 2.4.19. Quite a difference.

nice to hear! thanks.

  parent reply	other threads:[~2003-12-06  1:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04  2:49 2.4.23pre6aa3 scsi oops Jamie Clark
2003-11-04 10:28 ` Andrea Arcangeli
2003-11-04 11:52   ` Jamie Clark
2003-11-04 12:48     ` Andrea Arcangeli
2003-11-27  3:21     ` 2.4.23pre6aa3 - possible ext3 deadlock Jamie Clark
2003-11-27 12:56       ` Jan Kara
2003-12-06  1:05     ` Andrea Arcangeli [this message]
2003-12-06  1:39       ` 2.4.23pre6aa3 scsi oops Jamie Clark
2003-12-11  2:33       ` 2.4.23aa1 ext3 oops Jamie Clark
2003-12-16 15:15         ` Marcelo Tosatti
2003-12-16 15:55           ` Jamie Clark
2003-12-17 11:42         ` David Woodhouse
2003-12-18  6:19           ` Jamie Clark
2003-12-18  6:25             ` David Woodhouse
2003-12-18  7:33               ` Jamie Clark

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=20031206010505.GB14904@dualathlon.random \
    --to=andrea@suse.de \
    --cc=jamie@metaparadigm.com \
    --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 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.