From: Ed Tomlinson <edt@aei.ca>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Time sliced CFQ #3
Date: Mon, 6 Dec 2004 18:30:33 -0500 [thread overview]
Message-ID: <200412061830.33418.edt@aei.ca> (raw)
In-Reply-To: <20041206132749.GX10498@suse.de>
Jens,
This works here. Hope you keep patching against mainline. I`ve
decided to track it till 2.6.10 comes out...
Thanks,
Ed
On Monday 06 December 2004 08:27, Jens Axboe wrote:
> On Mon, Dec 06 2004, Prakash K. Cheemplavam wrote:
> > Jens Axboe schrieb:
> > >On Mon, Dec 06 2004, Prakash K. Cheemplavam wrote:
> > >
> > >>Hi,
> > >>
> > >>this one crapped out on me, while having heavy disk activity. (updating
> > >>gentoo portage tree - rebuilding metadata of it). Unfortunately I
> > >>couldn't save the oops, as I had no hd access anymore and X would freeze
> > >>a little later...(and I don't want to risk my data a second time...)
> > >
> > >
> > >Did you save anything at all? Just the function of the EIP would be
> > >better than nothing.
> >
> > Nope, sorry. I hoped it would be in the logs, but it seems as new cfq
> > went havoc, hd access went dead. And I was a bit too nervous about my
> > data so that I didn't write it down by hand...
>
> It is really rare for the io scheduler to cause serious data screwups,
> thankfully. Often what will happen is that it will crash, but with
> everything written fine up to that point. So it's similar to a power
> loss, but the drive should get it's cache out on its own.
>
> > >Well hard to say anything qualified without an oops :/
> > >
> > >I'll try with PREEMPT here.
> >
> > If you are not able to reproduce, I will try it again on a spare
> > partition... Should access to zip drive stil be possible if hd's
> > io-scheduler is dead?
>
> Depends on where it died, really. But the chances are probably slim.
>
> If you feel like giving it another go, I've uploaded a new patch here:
>
> http://www.kernel.org/pub/linux/kernel/people/axboe/patches/v2.6/2.6.10-rc3/cfq-time-slices-6.gz
>
> Changes:
>
> - Increase async_rq slice significantly (from 8 to 128)
>
> - Fix accounting bug that prevented non-fs requests from working
> correctly. Things like cdrecord and cdda rippers would hang.
>
> - Add logic to check whether a given process is potentially runnable or
> not. We don't arm the slice idle timer if the process has exited or is
> not either running or about to be running.
>
> - TCQ fix: don't idle drive until last request comes in.
>
> - Fix a stall with exiting task holding the active queue. This should
> fix Helges problems, I hope.
>
> - Restore ->nr_requests on io scheduler switch
>
> - Kill ->pid from io_context, this seems to have been added with 'as'
> but never used by anyone.
>
>
prev parent reply other threads:[~2004-12-06 23:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 10:49 [PATCH] Time sliced CFQ #2 Jens Axboe
2004-12-04 16:39 ` Jeff Sipek
2004-12-05 18:58 ` Jens Axboe
2004-12-06 0:29 ` Jeff Sipek
2004-12-06 1:59 ` Con Kolivas
2004-12-06 2:23 ` Jeff Sipek
2004-12-06 2:34 ` Con Kolivas
2004-12-06 5:00 ` Kyle Moffett
2004-12-06 5:14 ` Robert Love
2004-12-06 7:19 ` Jens Axboe
2004-12-06 12:18 ` Helge Hafting
2004-12-06 12:24 ` Jens Axboe
2004-12-06 12:21 ` Kyle Moffett
2004-12-06 16:42 ` Robert Love
2004-12-06 17:42 ` P
2004-12-06 7:15 ` Jens Axboe
2004-12-06 7:13 ` Jens Axboe
2004-12-05 14:21 ` Ed Tomlinson
2004-12-05 15:18 ` Jens Axboe
2004-12-05 17:58 ` Ed Tomlinson
2004-12-06 9:31 ` Prakash K. Cheemplavam
2004-12-06 9:35 ` Jens Axboe
2004-12-06 11:48 ` Ed Tomlinson
2004-12-06 12:31 ` Prakash K. Cheemplavam
2004-12-06 13:27 ` [PATCH] Time sliced CFQ #3 Jens Axboe
2004-12-06 14:01 ` Søren Lott
2004-12-06 15:01 ` Jens Axboe
2004-12-06 15:45 ` Jens Axboe
2004-12-06 15:07 ` Prakash K. Cheemplavam
2004-12-06 23:30 ` Ed Tomlinson [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=200412061830.33418.edt@aei.ca \
--to=edt@aei.ca \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox