From: Andrea Arcangeli <andrea@suse.de>
To: Mario Vanoni <vanonim@dial.eunet.ch>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: NFS problem after 2.4.19-pre3, not solved
Date: Fri, 10 May 2002 23:17:07 +0200 [thread overview]
Message-ID: <20020510231707.M13730@dualathlon.random> (raw)
In-Reply-To: <3CDC4962.4B9393D7@dial.eunet.ch>
On Fri, May 10, 2002 at 10:27:46PM +0000, Mario Vanoni wrote:
> Hi Trond, hi Andrea, hi All
>
> In production environment, since >6 months,
> ethernet 10Mbits/s, on backup_machine
> mount -t nfs production_machine /mnt.
>
> find `listing from production_machine` | \
> cpio -pdm backup_machine
>
> Volume ~320MB, nearly constant.
>
> Medium times:
>
> 2.4.17-rc1aa1: 1m58s, _the_ champion !!!
>
> all later's, e.g.:
>
> 2.4.19-pre8aa2; 4m35s
> 2.4.19-pre8-ac1: 4m00s
> 2.4.19-pre7-rmap13a: 4m02s
> 2.4.19-pre7: 4m35s
> 2.4.19-pre4: 4m20s
>
> the last usable was:
>
> 2.4.19-pre3: 2m35s, _not_ a champion
>
> All benchmarks don't reflect
> some production needs,
> <2 minutes or >4 minutes
> is a great difference !!!
Yep.
Some time ago you told me and Trond that 2.4.19pre8 + this below below
patch applied on top of 2.4.19pre4 returned back to the 2.4.19pre3 2.35
levels (the 1.58-2.35 difference could be not nfs related, and I want to
get to 2.35 first, 2.35-4.20 is a nfs thing).
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.19pre8aa2/00_nfs-backout-cto-1
Could you double check that's the patch that makes the difference if
applied on top of a vanilla 2.4.19pre4?
I cannot figure out why such a patch applied to pre4 fixes the problem,
while it doesn't fix the problem if applied to my tree.
Maybe it wasn't that patch that fixed your problem after all, but one of
the other nfs patches included in pre4. It would be very helpful if you
could double check, just in case.
Many thanks for the feedback! :)
Andrea
next prev parent reply other threads:[~2002-05-10 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 22:27 NFS problem after 2.4.19-pre3, not solved Mario Vanoni
2002-05-10 21:17 ` Andrea Arcangeli [this message]
2002-05-11 21:37 ` Mario Vanoni
2002-05-12 23:48 ` Trond Myklebust
2002-05-13 16:40 ` Andrea Arcangeli
2002-05-14 8:06 ` Trond Myklebust
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=20020510231707.M13730@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=vanonim@dial.eunet.ch \
/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