[LU-6704] Make checksum speeds available via /proc or /sys

• Status: Resolved
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Stephen Champion
• Assignee: Yang Sheng
• Resolution: Won't Fix
• Labels: easy, patch
• Severity: 3

Description

From LU-2212 -

Something like:
checksum_stats:

• crc32: { speed: 3568 MB/s, active: no }
• adler32: { speed: 4356 MB/s, active: yes }
• crc32c: { speed: 3668 MB/s, active: no }

Comments

[Stephen Champion]

Patch in progress.

[Gerrit Updater]

Stephen Champion ([e-mail]) uploaded a new patch: http://review.whamcloud.com/15193
Subject: LU-6704 osc: improve checksum_type parameter
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: e048b345abd7149c00851baaacb1b9299d7b3e9e

[Stephen Champion]

http://review.whamcloud.com/#/c/15193/

[Peter Jones]

Yang Sheng

Could you please take care of this patch?

Thanks

Peter

[Stephen Champion]

I had seen Andreas comment in LU-2212, and thought "good idea!". But now that I have a working version of this patch, it turns out it's not really very useful for what I'm doing, and I'm happy to abandon it - although it is nice to have the speed information in this context, so may be worth keeping.

For background - I'm looking at unexpected characteristics of hash algorithm availability to clients, and thought it was annoying that I had to enable info debug at module init to get speed test results. I'd actually like to expose the speed test results via procs (and later sysfs) on both clients and servers.

Would it make sense to just dump the speed results under /proc/sys/lnet/?

[Andreas Dilger]

Having the checksum speed available is useful, but I agree that changing the existing /proc file also causes problems with interoperability so it makes more sense to expose this information in a separate /proc file. Note that files under /proc/sys/lnet are one value per file, since these are moving into /sys in the upstream kernel which also requires this.