All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Matthias Hanisch <mjh@vr-web.de>,
	Mikael Pettersson <mikpe@csd.uu.se>,
	Linus Torvalds <torvalds@transmeta.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] 2.5.2 scheduler code for 2.4.18-pre1 ( was 2.5.2-pre performance degradation on an old 486 )
Date: Mon, 7 Jan 2002 08:32:56 +0100	[thread overview]
Message-ID: <20020107083256.B1755@suse.de> (raw)
In-Reply-To: <20020106112129.D8673@suse.de> <Pine.LNX.4.40.0201061554410.933-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.40.0201061554410.933-100000@blue1.dev.mcafeelabs.com>

On Sun, Jan 06 2002, Davide Libenzi wrote:
> > Davide,
> >
> > If this is caused by ISA bounce problems, then you should be able to
> > reproduce by doing something ala
> >
> > [ drivers/ide/ide-dma.c ]
> >
> > ide_toggle_bounce()
> > {
> > 	...
> >
> > +	addr = BLK_BOUNCE_ISA;
> > 	blk_queue_bounce_limit(&drive->queue, addr);
> > }
> >
> > pseudo-diff, just add the addr = line. Now compare performance with and
> > without your scheduler changes.
> 
> I fail to understand where the scheduler code can influence this.
> There's basically nothing inside blk_queue_bounce_limit()

Eh of course not, no time will be spent inside blk_queue_bounce_limit. I
don't think you looked very long at this :-)

The point is that ISA bouncing will spend some time scheduling waiting
for available memory in the __GFP_DMA zone.

-- 
Jens Axboe


  parent reply	other threads:[~2002-01-07  7:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-05  0:51 2.5.2-pre performance degradation on an old 486 Mikael Pettersson
2002-01-05  8:25 ` Matthias Hanisch
2002-01-05 23:10   ` Davide Libenzi
2002-01-06 10:21     ` Jens Axboe
2002-01-06 10:33       ` Andre Hedrick
2002-01-06 23:59       ` [patch] 2.5.2 scheduler code for 2.4.18-pre1 ( was 2.5.2-pre performance degradation on an old 486 ) Davide Libenzi
2002-01-07  1:38         ` Andrea Arcangeli
2002-01-07 14:35           ` J.A. Magallon
2002-01-07 14:37             ` Andrea Arcangeli
2002-01-07  7:32         ` Jens Axboe [this message]
2002-01-07 18:10           ` Davide Libenzi
2002-01-07  7:22     ` 2.5.2-pre performance degradation on an old 486 Matthias Hanisch
2002-01-07 16:43       ` Linus Torvalds
2002-01-07 18:31       ` Davide Libenzi
2002-01-07 21:43         ` Matthias Hanisch
2002-01-07 22:17           ` Davide Libenzi
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07  1:33 [patch] 2.5.2 scheduler code for 2.4.18-pre1 ( was 2.5.2-pre performance degradation on an old 486 ) Mikael Pettersson
2002-01-07  2:36 ` Davide Libenzi
2002-01-07  7:33   ` Jens Axboe
2002-01-07 18:12     ` Davide Libenzi

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=20020107083256.B1755@suse.de \
    --to=axboe@suse.de \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=mjh@vr-web.de \
    --cc=torvalds@transmeta.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 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.