OCFS2: Add trace event and replace mlog(0).
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 34 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 34 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Ocfs2-devel] [PATCH 00/34] OCFS2: Add trace event and replace mlog(0).
Quoted 11 lines · Joel Becker
I think what matters to count is dirs, because files disappear
when you're not using them.
If you have 319 trace event directories, that's 319 inodes. On
my x86, a vanilla struct inode is 360 bytes and a dentry is 136 bytes. That's 154K always in RAM for these knobs. I gotta say that I'm not too worried about 154K. Onx86_64(ca-build24) this grows to 241K. I imagine it will double when cluster and dlm are moved to similar trace events.
Are we OK with 300K on x86 and 500K onx86_64always used up by
these tracing entries?
I'm ok with that.