ocfs2: Inode Allocation Strategy Improvement.v2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 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 0/3] ocfs2: Inode Allocation Strategy Improvement.v2
Quoted 14 lines · tristan.ye
Quoted 3 lines · Sunil Mushran
How big is this disk? Maybe one kernel tree untar is not be enough to expose the original issue. Also, use ls -i and/or debugfs to see if the inodes have some locality.
Tao, sunil
I've tested it out with more attempts, it may have something to do with the disk size. but the root pause why i did not get a excited speed-up performance gain was due to the iscsi-target(iscsi server) cache. the operation in your testcase which was meant for cache dropping is aimed at client
side(a 'echo 2>/proc/sys/vm/drop_cache' only flush the fs's cache for iscsi initor(isci client)).
Quoted 7 lines
Tao,
You can verify this by pausing the tests at the right point before we start '2rd ls -lR', then flush the iscsi-target's cache by 'service iscsi-target restart'(there may be a more graceful way to do this),after this done, resume the tests, then you'll find the the realtime it consumed will be up to 3 mins around:)
cool, so I am very glad that you got the same result as mine. ;)
Quoted 4 lines
Btw, i really saw lots of locality by 'ls -li' for inodes under a same dir, take
/mnt/ocfs2/linux-2.6.28/include/linuxfor instance, almost all of its inodes are contiguous one by one regarding to its inode number.
yeah, that is the desired behaviour with my 3 patches. :)
Then do you have any updated test statistics?
Regards,
Tao