From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: paulmck@linux.vnet.ibm.com, eric.dumazet@gmail.com
Subject: [PATCH 0/2] xfs: RCU inode freeing and lookups V2
Date: Mon, 29 Nov 2010 11:50:24 +1100 [thread overview]
Message-ID: <1290991826-20714-1-git-send-email-david@fromorbit.com> (raw)
This series converts the XFS inode cache to use SLAB_DESTROY_BY_RCU
for freeing of the inodes and uses RCU locking for all the lookups.
It uses the ip->i_ino values and ip->i_flags & XFS_IRECLAIM being
checked under the ip->i_flags_lock to detect inodes that have been
freed during lookups.
Version 2:
- check ip->i_ino under i_flags lock on cache hit
- remove duplicate ip->i_ino == 0 check in xfs_dqrele_inode
- Fixed inode cluster walks to check for valid i_ino under
i_flags_lock.
- Fixed ag walk lookups to check i_ino under i_flags_lock.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-29 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:50 Dave Chinner [this message]
2010-11-29 0:50 ` [PATCH 1/2] xfs: convert inode cache lookups to use RCU locking Dave Chinner
2010-11-29 0:50 ` [PATCH 2/2] xfs: convert pag_ici_lock to a spin lock Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1290991826-20714-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=eric.dumazet@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox