From: Tejun Heo <tj@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: hmajxxlh@corbac.com, fuse-devel@lists.sourceforge.net,
mszeredi@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [fuse-devel] OSS Proxy Jack slave
Date: Thu, 10 Jun 2010 17:26:53 +0200 [thread overview]
Message-ID: <4C11043D.3040500@kernel.org> (raw)
In-Reply-To: <E1OMhnk-0005i4-8F@pomaz-ex.szeredi.hu>
Hello,
On 06/10/2010 03:28 PM, Miklos Szeredi wrote:
> On Thu, 10 Jun 2010, Tejun Heo wrote:
> I'm sure its a good idea to provide an interface that does't _require_
> server side mmaps. This doesn't preclude an mmap interface later on,
> but I'd rather start with a "pure" read/write device interface, which
> is in a lot of ways simpler to solve than mmap.
It doesn't preclude that but then again having two interfaces can be a
bit silly.
> As for pinning kernel pages, I still think it's a good idea for the
> char device interface, but you're right, it's not necessary.
>
> In fact I'm mostly ready with an implementation of store/retrieve that
> just pokes the regular page cache.
But I think if we can avoid using pinned kernel pages, pure r/w based
implementation could be different and useful enough, so yeah, great.
Thanks.
--
tejun
prev parent reply other threads:[~2010-06-10 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100601092456.GA23572@alia.nute.net>
[not found] ` <4C066CF4.2050902@gmail.com>
[not found] ` <20100605085045.GA5630@alia.nute.net>
2010-06-05 9:05 ` OSS Proxy Jack slave Tejun Heo
2010-06-09 10:08 ` [fuse-devel] " Miklos Szeredi
2010-06-10 11:23 ` Tejun Heo
2010-06-10 11:52 ` Miklos Szeredi
2010-06-10 13:13 ` Tejun Heo
2010-06-10 13:28 ` Miklos Szeredi
2010-06-10 15:26 ` 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=4C11043D.3040500@kernel.org \
--to=tj@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hmajxxlh@corbac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
/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