[PATCH v3 00/13] xfs: kill hard-coded number 128 for transaction space log reservation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Now the v3 patch set of killing hard-coded number 128 for transaction space log
reservation is ready for review.

For testing, according to Dave's comment, I verified the default/patched kernel by
comparing the total bytes per transaction as well as the pair values in MAX() against
the different combinations of block /log/inode/sector sizes, and they all show the same
results to me. 


Changes of v3 to v2:
- Fix itruncate, ifree, link, attrrm, remove, create to show correct results.
- Add XFS_SB_LOG_RES() for those transactions that modify the super block on disk.


Old patch sets:
v2:
http://www.spinics.net/lists/xfs/msg15917.html
v1:
http://www.spinics.net/lists/xfs/msg15499.html

Thanks,
-Jeff

_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs


[Index of Archives]     [Linux XFS Devel]     [Linux Filesystem Development]     [Filesystem Testing]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux