aboutsummaryrefslogtreecommitdiff
path: root/include/asm-m68knommu/dma.h
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@redhat.com>2008-04-28 02:16:10 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2008-04-28 08:58:44 -0700
commit5bc833feaa8b2236265764e7e81f44937be46eda (patch)
tree9aa34ee4e898d268fade3e6e2b9b5678f49caa54 /include/asm-m68knommu/dma.h
parent269b26191650be46ce6c91dec24cf20f59650529 (diff)
jbd: fix the way the b_modified flag is cleared
Currently at the start of a journal commit we loop through all of the buffers on the committing transaction and clear the b_modified flag (the flag that is set when a transaction modifies the buffer) under the j_list_lock. The problem is that everywhere else this flag is modified only under the jbd lock buffer flag, so it will race with a running transaction who could potentially set it, and have it unset by the committing transaction. This is also a big waste, you can have several thousands of buffers that you are clearing the modified flag on when you may not need to. This patch removes this code and instead clears the b_modified flag upon entering do_get_write_access/journal_get_create_access, so if that transaction does indeed use the buffer then it will be accounted for properly, and if it does not then we know we didn't use it. That will be important for the next patch in this series. Tested thoroughly by myself using postmark/iozone/bonnie++. Signed-off-by: Josef Bacik <jbacik@redhat.com> Cc: <linux-ext4@vger.kernel.org> Acked-by: Jan Kara <jack@ucw.cz> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/asm-m68knommu/dma.h')
0 files changed, 0 insertions, 0 deletions