From: David Nicol <davidnicol@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Miao Xie <miaox@cn.fujitsu.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Itaru Kitayama <kitayama@cl.bb4u.ne.jp>
Subject: Re: [PATCH V2] btrfs: implement delayed inode items operation
Date: Fri, 4 Mar 2011 21:44:29 -0600 [thread overview]
Message-ID: <AANLkTikr21czNX=OsWH3JKAFdYzcsAkE-eqQiGOzDosV@mail.gmail.com> (raw)
In-Reply-To: <1297991261-sup-6831@think>
On Thu, Feb 17, 2011 at 7:09 PM, Chris Mason
>
> This work is really cool, thanks for doing it. =C2=A0I'm starting a r=
un on
> this tonight and if all goes well I'll review in detail and try to qu=
eue
> it along with the per-subvolume storage bits for .39.
>
> Thanks!
>
> -chris
This is the kind of thing -- another synchronous thing becomes
asynchronous -- why the ioctl#21 patch has a pluggable architecture
for adding a standard way to wait for completion of new dlayed items.
Please add it, so future submitted ways to asynchonify things can have
a standard way to tell when they're done.
dln
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-05 3:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 5:48 [PATCH V2] btrfs: implement delayed inode items operation Miao Xie
2011-02-18 1:09 ` Chris Mason
2011-02-18 9:08 ` Miao Xie
2011-02-18 12:19 ` Chris Mason
2011-02-18 13:09 ` Miao Xie
2011-02-18 14:35 ` Chris Mason
2011-02-22 9:58 ` Miao Xie
2011-03-05 3:44 ` David Nicol [this message]
2011-02-18 13:30 ` David Sterba
2011-02-18 14:13 ` Miao Xie
-- strict thread matches above, loose matches on Subject: below --
2011-02-24 14:02 Itaru Kitayama
2011-03-03 6:15 ` Miao Xie
2011-03-05 2:35 ` Itaru Kitayama
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='AANLkTikr21czNX=OsWH3JKAFdYzcsAkE-eqQiGOzDosV@mail.gmail.com' \
--to=davidnicol@gmail.com \
--cc=chris.mason@oracle.com \
--cc=kitayama@cl.bb4u.ne.jp \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).