mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Robert Macaulay <robert_macaulay@dell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.57 IO slowdown with CONFIG_PREEMPT enabled
Date: Thu, 16 Jan 2003 03:51:09 -0800	[thread overview]
Message-ID: <20030116035109.64d1ef97.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301151712350.23847-100000@ping.us.dell.com>

Robert Macaulay <robert_macaulay@dell.com> wrote:
>
> On Wed, 15 Jan 2003, Andrew Morton wrote:
> > if you could please test that with CONFIG_PREEMPT=y
> 
> Reverting that brings the speed back up

OK.  How irritating.

Presumably there's a fairness problem - once a CPU goes in there to start
spinning on the lock, the length of the loop is such that it's easy for
non-holders to zoom in and claim it first.  Or something.

Unless another way of solving the problem which that patch solves presents
itself we may need to revert it.

Or not.  Should a CONFIG_PREEMPT SMP kernel compromise its latency because of
overused locking??


I'd appreciate it if you could take a closer look at the mysterious
self-reverting .config, please.  See if you can work out what is causing it,
tell me how you're rebooting (reboot -f?  -fn?  Big Red Button?) and whether
the offending file is on the root filesystem, etc.


Thanks.

  reply	other threads:[~2003-01-16 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 17:36 Robert Macaulay
2003-01-15 18:01 ` Andrew Morton
2003-01-15 19:18 ` Andrew Morton
2003-01-15 22:12   ` Robert Macaulay
2003-01-15 22:33     ` Andrew Morton
2003-01-15 22:46       ` Robert Macaulay
2003-01-15 23:20       ` Robert Macaulay
2003-01-16 11:51         ` Andrew Morton [this message]
2003-01-16 16:14           ` Robert Macaulay

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=20030116035109.64d1ef97.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert_macaulay@dell.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

Powered by JetHome