From: Jeff Liu <jeff.liu@oracle.com>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: [PATCH 0/10] xfs: xfs_ioc_bulkstat refactoring and consolidation
Date: Sat, 28 Dec 2013 19:19:42 +0800 [thread overview]
Message-ID: <52BEB3CE.5000303@oracle.com> (raw)
Hi Folks,
The parallel quota check is still in progress because I observed performance number
varies greatly, I suspect that is related to the hardward problem of my laptop.
Thus, I have to delay that for a period of time until I can get a reasonable results.
Meantime, there are some patches could be posted for the review which are focus on
code refactoring and consolidations in xfs_ioc_bulkstat() related functions, i.e,
xfs_bulkstat(), xfs_inumbers(), etc...
It mainly implemented per AG bulkstat that we have discussed in parallel quota check
thread, and fix several problems regarding to the error handling for inode btree
operations in xfs_bulkstat() and xfs_inumbers() as per Christoph's suggestion.
Moreover, I introduced another per AG inumber strategy, which can be used to scan
multiple AGs with a new ioctl(2) in the future.
Thanks,
-Jeff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2013-12-28 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52BEB3CE.5000303@oracle.com \
--to=jeff.liu@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.