From: Tejun Heo <tj@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, fuse-devel@lists.sourceforge.net
Subject: Re: [PATCHSET] CUSE: implement CUSE, take #3
Date: Sat, 09 May 2009 08:35:04 +0900 [thread overview]
Message-ID: <4A04C1A8.2070904@kernel.org> (raw)
In-Reply-To: <E1M1dVf-00051D-JE@pomaz-ex.szeredi.hu>
Miklos Szeredi wrote:
> On Thu, 30 Apr 2009, Tejun Heo wrote:
>> Tejun Heo wrote:
>>>> I'll post the updated libfuse patch as well. Please let me know if
>>>> you find anything wrong with the current patches.
>>> Looks good to me. Much prettier with two inits merged.
>> Oh... what happened to CUSE_INIT_DONE?
>
> By moving the CUSE_INIT reply processing into the ->end() callback,
> the device initialization becomes synchronous with the process writing
> the message into the cuse device.
>
> This means, that the process can simply wait for the write() on the
> device to complete before proceeding.
>
> I've updated the libfuse patch so it calls ->init_done() after sending
> the CUSE_INIT reply.
Ah... cool. Thanks.
--
tejun
prev parent reply other threads:[~2009-05-08 23:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 1:54 [PATCHSET] CUSE: implement CUSE, take #3 Tejun Heo
2009-04-14 1:54 ` [PATCH 1/6] FUSE: misc cleanups Tejun Heo
2009-04-14 1:54 ` [PATCH 2/6] FUSE: use fuse objects as the main objects in file handling functions Tejun Heo
2009-04-14 1:54 ` [PATCH 3/6] FUSE: make ff->fi optional Tejun Heo
2009-04-14 1:54 ` [PATCH 4/6] FUSE: update fuse_conn_init() and separate out fuse_conn_kill() Tejun Heo
2009-04-14 1:54 ` [PATCH 5/6] FUSE: export symbols to be used by CUSE Tejun Heo
2009-04-14 1:54 ` [PATCH 6/6] CUSE: implement CUSE - Character device in Userspace Tejun Heo
2009-04-21 16:43 ` [PATCHSET] CUSE: implement CUSE, take #3 Tejun Heo
2009-04-22 11:39 ` Miklos Szeredi
2009-04-23 0:09 ` Tejun Heo
2009-04-23 10:08 ` Miklos Szeredi
2009-04-23 10:32 ` Tejun Heo
2009-04-28 15:43 ` Miklos Szeredi
2009-04-30 2:10 ` Tejun Heo
2009-04-30 2:13 ` Tejun Heo
2009-05-06 9:33 ` Miklos Szeredi
2009-05-08 23:35 ` Tejun Heo [this message]
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=4A04C1A8.2070904@kernel.org \
--to=tj@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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