https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-24 Lustre <p>(Lustre bugzilla 15646 - LNET selftest to measure latency)<br/> (Lustre bugzilla 17328 - minor issue for lnet selftest)</p> <p>Intention is to:</p> <ul> <li>Bring Liang's stats cleanup (bz17328 att 21207) up to master.</li> <li>Make the ping test use the png_size parameter</li> <li>Report latency measured from the ping test in lst stat.</li> </ul> <p>Also various typos in messages, and want to sort out the way that utils/lst lets you put in any old size for the brw test, but in the lnet_selftest module it gets rounded down to the nearest page.</p> LU-24

LNET selftest improvements

Improvement Minor Resolved Incomplete John Spray John Spray Thu, 16 Dec 2010 02:14:54 +0000 Wed, 17 Apr 2013 21:58:21 +0000 Wed, 17 Apr 2013 21:58:21 +0000 Lustre 2.0.0 Lustre 2.1.0 Lustre 1.8.6 Mon, 20 Dec 2010 00:00:00 +0000 0 4 <p>John, I made a quick look through this patch, seems you are improving current ping_test to make it support ping_size and measure latency. <br/> It's not a problem if all nodes in cluster upgrade to the same version with this patch in the future, but if customer can't upgrade all nodes in one batch (i.e: some nodes are using 1.8.x and some are using 2.x), then they can't use LST anymore because this patch have changed some wired data (structures with WIRE_ATTR).<br/> Probably we can add a new command like "ping_pro" or "ping_adv" to LST, and add some wired structures (request/reply) for this new command, so even customer upgraded some of their nodes, they still can use LST with regular "lst ping"</p> <p>How do you think?</p> <p>Here's a hopefully backwards-compatible version &#8211; there's quite of a lot of code, because the stats reply structure didn't have any spare space for the ping stats.</p> <p>The existing stats request structure did have a 'str_type' field, but this wasn't being used. If we started using this, then old nodes would ignore it, and when querying them we wouldn't know whether they were returning something valid or not. However, the new 'XSTAT' type is quite verbose for not that much benefit, so we might want to tolerate a bit of ugliness to make the code shorter.</p> <p>Cleaning up: this has been idle for &gt;2yrs.</p> Bugzilla ID 15646.0 Development Rank 1|hzvofr: Rank (Obsolete) 7778