From: Droebbel <droebbel.melta@gmx.de>
To: Tino Keitel <tino.keitel@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Problem] slow write to dvd-ram since 2.6.7-bk8
Date: Wed, 16 Feb 2005 22:55:00 +0100 [thread overview]
Message-ID: <1108590900.7407.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20050214111819.GA7691@dose.home.local>
Some new information:
2.6.7 is ok, 2.6.7-mm2 is not ok, 2.6.7 with just the linus-patch from
mm2 is ok, 2.6.7 with linus.patch from mm3 isn't.
So I took some of the patches from the broken-out mm2 and tested them
seperately.
The vmscan-dont-reclaim-too-many-pages.patch led to the said reduction
of writing speed. I reverse-applied it to 2.6.8.1, where it seems to
solve the problem. I also reverse-applied it to the current prepatched
Ubuntu-2.6.10. It helped a bit there. Some new errors since 2.6.8, as it
seems... getting depressing a bit, this whole thing.
If you are using 2.6.7-mm1, there is another patch with even greater
impact: abs-fix.patch. Take the same + abs-fix-fix.patch from mm2.
If you might have a look at the vmscan-dont-reclaim-too-many-pages.patch
from
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm2/broken-out/, maybe you will find out something.
Comparing the abs-fix patches from mm1 and mm2 might also help.
This is all I can do for now.
Regards
David
next prev parent reply other threads:[~2005-02-16 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 13:36 Droebbel
2005-02-13 14:26 ` Wakko Warner
2005-02-14 8:53 ` Tino Keitel
2005-02-14 10:28 ` Droebbel
[not found] ` <1108376734.9495.8.camel@localhost.localdomain>
[not found] ` <20050214105332.GA7163@dose.home.local>
2005-02-14 12:34 ` Droebbel
[not found] ` <1108379351.9495.22.camel@localhost.localdomain>
[not found] ` <20050214111819.GA7691@dose.home.local>
2005-02-16 21:55 ` Droebbel [this message]
2005-02-16 22:29 ` Droebbel
2005-02-17 23:10 ` Tino Keitel
2005-02-18 22:21 ` Droebbel
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=1108590900.7407.11.camel@localhost.localdomain \
--to=droebbel.melta@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tino.keitel@gmx.de \
/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
all inboxes | Powered by JetHome®