All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mhf@linuxmail.org>
To: Nick Piggin <piggin@cyberone.com.au>,
	Nigel Cunningham <ncunningham@clear.net.nz>
Cc: cliff white <cliffw@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test8/test9 io scheduler needs tuning?
Date: Tue, 28 Oct 2003 15:48:14 +0800	[thread overview]
Message-ID: <200310281548.14510.mhf@linuxmail.org> (raw)
In-Reply-To: <3F9DE858.7020109@cyberone.com.au>

On Tuesday 28 October 2003 11:54, Nick Piggin wrote:
> 
> Nigel Cunningham wrote:
> 
> >As you rightly guessed, I was forgetting there are now 1000 jiffies per
> >second.
> >
> >With your patch applied, I can achieve something close to 2.4
> >performance, but only if I set the limit on the number of pages to
> >submit at one time quite high. If I set it to 3000, I can get 20107 4K
> >pages written in 5267 jiffies (14MB/s) and can read them back at resume
> >time (so cache is not a factor) in 4620 jiffies (16MB/s). In 2.4, I
> >normally set the limit on async commits to 100, and achieve the same
> >performance. 100 here makes it very jerky and much slower.
> >
> >Could there be some timeout value on BIOs that I might be able to
> >tweak/disable during suspend?
> >
> 
> Try setting /sys/block/xxx/queue/iosched/antic_expire to 0 on your
> device under IO and see how it goes. That shouldn't be causing the
> problem though, especially as you are mostly writing I think?
> 
> Otherwise might possibly be the queue plugging stuff, or maybe a
> regression in the disk driver.
> 

Haven't done much of 2.6 swsusp testing due to the little diversion
with the scheduler, however I did notice one of those dreaded DMA 
timeouts with the SIS chipset again.



Regards
Michael


  reply	other threads:[~2003-10-28  7:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 21:52 2.6.0-test8/test9 io scheduler needs tuning? Michael Frank
2003-10-27 22:55 ` cliff white
2003-10-27 23:50   ` Nick Piggin
2003-10-28  1:37     ` Nigel Cunningham
2003-10-28  1:48       ` Nick Piggin
2003-10-28  2:58         ` Michael Frank
2003-10-28  2:57       ` Michael Frank
2003-10-28  3:31       ` Nigel Cunningham
2003-10-28  3:54         ` Nick Piggin
2003-10-28  7:48           ` Michael Frank [this message]
2003-10-28  4:13     ` Michael Frank
2003-10-28  4:30       ` Nick Piggin
2003-10-28  6:11         ` Michael Frank
2003-10-28 17:42         ` Martin Josefsson
2003-10-28 17:26     ` cliff white
2003-10-28 21:18       ` Dave Olien
2003-10-29  2:40         ` Nick Piggin
2003-10-29  4:56           ` Michael Frank
2003-10-29 16:47             ` Michael Frank

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=200310281548.14510.mhf@linuxmail.org \
    --to=mhf@linuxmail.org \
    --cc=cliffw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@clear.net.nz \
    --cc=piggin@cyberone.com.au \
    /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.