All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Philippe Gramoulle <philippe.gramoulle@mmania.com>
Cc: ReiserFS Mailing List <reiserfs-list@namesys.com>
Subject: Re: Speedup patch for 2.4.19-pre6 in bitmap.c
Date: Wed, 10 Apr 2002 19:02:03 +0400	[thread overview]
Message-ID: <20020410190203.A22633@namesys.com> (raw)
In-Reply-To: <20020410165508.D54344@off.aspic.com>

Hello!

On Wed, Apr 10, 2002 at 04:55:08PM +0200, Philippe Gramoulle wrote:

> Here is the bitmap.c.rej:
> -   s->s_dirt = 1;

> Is this something i can blindly update by hand ,i mean manually remove "s->s_dirt = 1;" ?

Yes, just remove that line manually.

> At the moment i'm pretty surprised by the NFSv3 TCP performance:
> ( 6.32 Mb/s for a single dd if=/dev/zero of =testfile bs=8192 count=25000 , 200Mb file)
> ( average of 460 Kb/s when uploading a 184Mo compiled kernel tree through FTP)
> 
> Before that i manage to get 10Mb/s on an eepro100 with vanilla 2.4.18 and NFS_ALL TCP from Trond
> (either NFSv3 TCP or UDP)

So I assume you are negatively surprised, right?
And if you undo the speedup patch only, do you get your numbers back?
Also do you have highmem on for 2.4.19-pre6 kernel?

Bye,
    Oleg

  reply	other threads:[~2002-04-10 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 14:55 Speedup patch for 2.4.19-pre6 in bitmap.c Philippe Gramoulle
2002-04-10 15:02 ` Oleg Drokin [this message]
2002-04-10 15:09   ` Philippe Gramoulle
2002-04-10 15:13     ` Oleg Drokin
2002-04-10 18:48       ` Philippe Gramoulle
2002-04-10 19:05         ` Oleg Drokin
2002-04-10 19:09           ` Philippe Gramoulle
  -- strict thread matches above, loose matches on Subject: below --
2002-04-10 15:04 wolfgang.glas

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=20020410190203.A22633@namesys.com \
    --to=green@namesys.com \
    --cc=philippe.gramoulle@mmania.com \
    --cc=reiserfs-list@namesys.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.