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 15:13:33 +0200 [thread overview]
Message-ID: <869cdc8d-85cf-468e-8f94-ff50551684ba@email.android.com> (raw)
In-Reply-To: <E1OMgIz-0005Wb-2a@pomaz-ex.szeredi.hu>
Hello,
Nope, it's not required for osspd but it's a rather strong limitation on the interface which would be pretty difficult to work around later. Page protection tricks would be very cumbersome and unscalable. Hmmm, it does remove the necessity for allocating kernel pages, right? Still, it seems like a big limitation. Are you sure this is a good idea?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-06-10 13:14 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 ` 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 [this message]
2010-06-10 13:28 ` Miklos Szeredi
2010-06-10 15:26 ` Tejun Heo
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=869cdc8d-85cf-468e-8f94-ff50551684ba@email.android.com \
--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
Powered by JetHome