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

To:	xfs@xxxxxxxxxxx
Subject:	[PATCH v3 00/13] xfs: kill hard-coded number 128 for transaction space log reservation
From:	Jeff Liu <jeff.liu@xxxxxxxxxx>
Date:	Thu, 24 Jan 2013 19:09:18 +0800
Delivered-to:	xfs@xxxxxxxxxxx
User-agent:	Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2

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

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH v3 00/13] xfs: kill hard-coded number 128 for transaction space log reservation, Jeff Liu <=

Previous by Date:	Re: Copy file , file blocks is different, Dave Chinner
Next by Date:	[PATCH v3 01/13] xfs: add a helper to figure out the space log reservation per item, Jeff Liu
Previous by Thread:	Copy file , file blocks is different, Homer Li
Next by Thread:	[PATCH v3 01/13] xfs: add a helper to figure out the space log reservation per item, Jeff Liu
Indexes:	[Date] [Thread] [Top] [All Lists]