Per iclog callback chain lock
Rather than use the icloglock for protecting the iclog completion
callback chain, use a new per-iclog lock so that walking the
callback chain doesn't require holding a global lock.
This reduces contention on the icloglock during transaction commit
and log I/O completion by reducing the number of times we need to
hold the global icloglock during these operations.
Date: Wed Apr 9 13:47:24 AEST 2008
Workarea: chook.melbourne.sgi.com:/build/dgc/isms/2.6.x-xfs
Inspected by: lachlan@xxxxxxx,hch@xxxxxxxxxxxxx
The following file(s) were checked into:
longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb
Modid: xfs-linux-melb:xfs-kern:30770a
fs/xfs/xfs_log.c - 1.350 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_log.c.diff?r1=text&tr1=1.350&r2=text&tr2=1.349&f=h
- Use a per-iclog callback chain log to reduce contention on the
icloglock.
fs/xfs/xfs_log_priv.h - 1.128 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_log_priv.h.diff?r1=text&tr1=1.128&r2=text&tr2=1.127&f=h
- Use a per-iclog callback chain log to reduce contention on the
icloglock.
|