All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:29:24 +0100	[thread overview]
Message-ID: <1108592965.7407.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1108590900.7407.11.camel@localhost.localdomain>

On Mi, 2005-02-16 at 22:55 +0100, Droebbel wrote:
>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.

Sorry, have to correct that: it seemed to help at my tests with dd
(write 1G of zeroes to a file). Copying a file with mc still shows
around 1.4MB/s. Could be worse, but is definitely not ok. It *is* better
with 2.6.7.

Regards

David


  reply	other threads:[~2005-02-16 22:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-13 13:36 [Problem] slow write to dvd-ram since 2.6.7-bk8 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
2005-02-16 22:29               ` Droebbel [this message]
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=1108592965.7407.17.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 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.