| To: | dgc@xxxxxxx (David Chinner) |
|---|---|
| Subject: | Re: PARTIAL TAKE 964999 - lazy superblock counters for XFS |
| From: | Andi Kleen <andi@xxxxxxxxxxxxxx> |
| Date: | 24 May 2007 23:48:16 +0200 |
| Cc: | xfs@xxxxxxxxxxx, sgi.bugs.xfs@xxxxxxxxxxxx |
| In-reply-to: | <20070522075932.E665058CA531@chook.melbourne.sgi.com> |
| References: | <20070522075932.E665058CA531@chook.melbourne.sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 |
dgc@xxxxxxx (David Chinner) writes: > > The key to removing the contention is to not require the superblock > fields in question to be locked. We do that by not marking the > superblock dirty in the transaction. IOWs, we modify the incore > superblock but do not modify the cached superblock buffer. In short, > we do not log superblock modifications to critical fields in the > superblock on every transaction. In fact we only do it just before > we write the superblock to disk every sync period or just before > unmount. Does this mean it will increases performance on small systems too due to less super block writes or is it purely for large system scalability? -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: RESVSP problems, Åukasz Fibinger |
|---|---|
| Next by Date: | Re: PARTIAL TAKE 964999 - lazy superblock counters for XFS, David Chinner |
| Previous by Thread: | PARTIAL TAKE 964999 - lazy superblock counters for XFS, David Chinner |
| Next by Thread: | Re: PARTIAL TAKE 964999 - lazy superblock counters for XFS, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |