From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jason Holmes <jholmes@psu.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: 2.4 vs. 2.6 nfs client performance
Date: 12 Nov 2003 15:20:31 -0500 [thread overview]
Message-ID: <shssmkttk34.fsf@charged.uio.no> (raw)
In-Reply-To: <3FB27670.4C878A84@psu.edu>
>>>>> " " == Jason Holmes <jholmes@psu.edu> writes:
> Can someone clue me in as to why this may be happening and if
> it's a "bug" or not?
Large numbers of 'commit' operations are a typical sign of the memory
management going wild. Have you compared this to the standard
2.6.0-test9 kernel?
What sort of load did you otherwise have on that machine?
Cheers,
Trond
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-11-12 20:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 18:05 2.4 vs. 2.6 nfs client performance Jason Holmes
2003-11-12 20:20 ` Trond Myklebust [this message]
2003-11-12 20:51 ` Jason Holmes
2003-11-12 21:18 ` Trond Myklebust
2003-11-12 21:33 ` Jason Holmes
2003-11-12 23:22 ` Trond Myklebust
2003-11-13 1:20 ` Jason Holmes
2003-11-13 2:07 ` Trond Myklebust
2003-11-13 14:16 ` Jason Holmes
2003-11-13 21:55 ` Jason Holmes
2003-11-14 0:22 ` Trond Myklebust
2003-11-14 18:37 ` Jason Holmes
2003-11-14 21:11 ` Trond Myklebust
2003-11-16 15:54 ` Jason Holmes
2003-11-13 15:56 ` Eric Whiting
2003-11-13 17:55 ` Trond Myklebust
2003-11-13 18:59 ` Eric Whiting
2003-11-13 19:09 ` Eric Whiting
2003-11-13 19:28 ` Trond Myklebust
2003-11-13 19:18 ` Jason Holmes
2003-11-12 22:08 ` Eric Whiting
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 19:42 Duc Vianney
2003-11-13 20:02 ` 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=shssmkttk34.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=jholmes@psu.edu \
--cc=nfs@lists.sourceforge.net \
/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