linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Seger, Mark" <mark.seger@hp.com>
To: "util-linux-ng@vger.kernel.org" <util-linux-ng@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: New release of collectl now supports NFS V4 and buddyinfo
Date: Thu, 12 Mar 2009 13:14:15 +0000	[thread overview]
Message-ID: <9FCE3A46FE7C8045A6207AE4B42E9F9A4792FDA420@GVW1119EXC.americas.hpqcorp.net> (raw)
In-Reply-To: <477FDAA8.2030001@hp.com>

Just a quick note on this.  If you've been staying away from collectl because it didn't support V4 of nfs, I finally got around to adding it.  One thing that's kind of cool is if you run the command "collectl -sF --home", you'll see a top-like command that displays most of the nfs stats on all types of the systems' nfs client/servers for versions 2,3 and 4.  You can read a little more about it at: http://collectl.sourceforge.net/NfsInfo.html

While I was at it I also added buddyinfo monitoring, so you can literally watch your fragment distribution change in real-time using the command "collectl -sB --home" as described here - http://collectl.sourceforge.net/BuddyInfo.html.  I'm still not sure how one can make the most out of this information or if I'm displaying it in the most useful manner, but as always all feedback is welcome, preferably on the collectl mailing list collectl-interest@lists.sourceforge.net.

-mark


 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2009-03-12 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 19:29 Supports for new slab allocator now in latest release Mark Seger
2009-03-12 13:14 ` Seger, Mark [this message]

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=9FCE3A46FE7C8045A6207AE4B42E9F9A4792FDA420@GVW1119EXC.americas.hpqcorp.net \
    --to=mark.seger@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=util-linux-ng@vger.kernel.org \
    /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