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>
Date: Thu, 12 Mar 2009 13:14:15 +0000
Subject: New release of collectl now supports NFS V4 and buddyinfo
Thread-Topic: New release of collectl now supports NFS V4 and buddyinfo
Thread-Index: AcmjFHF3Va8IFjbmTcCGwmkZycgzXw==
Message-ID: <9FCE3A46FE7C8045A6207AE4B42E9F9A4792FDA420@GVW1119EXC.americas.hpqcorp.net>
References: <477FDAA8.2030001@hp.com>
In-Reply-To: <477FDAA8.2030001@hp.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1180
Lines: 14

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/