From: Miklos Szeredi <miklos@szeredi.hu>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
fuse-devel@lists.sourceforge.net,
Ashish Samant <ashish.samant@oracle.com>,
Srinivas Eeda <srinivas.eeda@oracle.com>
Subject: fuse scalability part 1
Date: Mon, 18 May 2015 17:13:36 +0200 [thread overview]
Message-ID: <20150518151336.GA9960@tucsk> (raw)
This part splits out an "input queue" and a "processing queue" from the
monolithic "fuse connection", each of those having their own spinlock.
The end of the patchset adds the ability to "clone" a fuse connection. This
means, that instead of having to read/write requests/answers on a single fuse
device fd, the fuse daemon can have multiple distinct file descriptors open.
Each of those can be used to receive requests and send answers, currently the
only constraint is that a request must be answered on the same fd as it was read
from.
This can be extended further to allow binding a device clone to a specific CPU
or NUMA node.
Patchset is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
Libfuse patches adding support for "clone_fd" option:
git://git.code.sf.net/p/fuse/fuse clone_fd
Thanks,
Miklos
next reply other threads:[~2015-05-18 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 15:13 Miklos Szeredi [this message]
2015-09-24 1:13 ` fuse scalability part 1 Ashish Samant
[not found] ` <20150814101453.GB31364@frosties>
2015-09-24 6:30 ` [fuse-devel] " Miklos Szeredi
2015-09-24 19:17 ` Ashish Samant
2015-09-25 12:11 ` Miklos Szeredi
2015-09-25 17:53 ` Ashish Samant
2015-09-29 6:18 ` Srinivas Eeda
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=20150518151336.GA9960@tucsk \
--to=miklos@szeredi.hu \
--cc=ashish.samant@oracle.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.eeda@oracle.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).