From: Chris Mason <chris.mason@oracle.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
Itaru Kitayama <kitayama@cl.bb4u.ne.jp>,
Ito <t-itoh@jp.fujitsu.com>, David Sterba <dave@jikos.cz>
Subject: Re: [PATCH V5 2/2] btrfs: implement delayed inode items operation
Date: Sat, 26 Mar 2011 19:58:10 -0400 [thread overview]
Message-ID: <1301183781-sup-1324@think> (raw)
In-Reply-To: <4D8B2DEB.1000001@cn.fujitsu.com>
Excerpts from Miao Xie's message of 2011-03-24 07:41:31 -0400:
> Changelog V4 -> V5:
> - Fix the race on adding the delayed node to the inode, which is spotted by
> Chris Mason.
> - Merge Chris Mason's incremental patch into this patch.
> - Fix deadlock between readdir() and memory fault, which is reported by
> Itaru Kitayama.
This does do much better than v4, but I'm still hitting oom with
stress.sh -n 50. I tried a bunch of variations but haven't been able to
get it quite right. I think I need to hold off on this one and get the
2.6.39 pull request out.
I'll setup a .40 tree that has this in it and we can fix the ooms. This
is a great base for the work, and I'd like to add more items to the
delay, especially the initial inode insertions.
-chris
next prev parent reply other threads:[~2011-03-26 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 11:41 [PATCH V5 2/2] btrfs: implement delayed inode items operation Miao Xie
2011-03-24 23:55 ` David Sterba
2011-03-26 23:58 ` Chris Mason [this message]
2011-03-27 5:30 ` Itaru Kitayama
2011-03-27 7:00 ` Miao Xie
2011-03-27 11:09 ` Itaru Kitayama
2011-03-27 11:44 ` Miao Xie
2011-03-27 11:42 ` Chris Mason
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=1301183781-sup-1324@think \
--to=chris.mason@oracle.com \
--cc=dave@jikos.cz \
--cc=kitayama@cl.bb4u.ne.jp \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=t-itoh@jp.fujitsu.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.