linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <mszeredi@redhat.com>
To: Boaz Harrosh <boazh@netapp.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	lsf-pc@lists.linux-foundation.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Ric Wheeler <rwheeler@redhat.com>, Jan Kara <jack@suse.cz>,
	Steven Whitehouse <swhiteho@redhat.com>,
	Tom Coughlan <coughlan@redhat.com>,
	Jeff Moyer <jmoyer@redhat.com>, Sage Weil <sweil@redhat.com>,
	Andy Rudof <andy.rudoff@intel.com>,
	Anna Schumaker <Anna.Schumaker@netapp.com>,
	Amir Goldstein <amir73il@gmail.com>,
	Stephen Bates <stephen@eideticom.com>,
	Amit Golander <Amit.Golander@netapp.com>,
	Sagi Manole <sagim@netapp.com>,
	Shachar Sharon <Shachar.Sharon@netapp.com>,
	Josef Bacik <josef@redhat.com>
Subject: Re: [LSF/MM TOPIC ATTEND][RFD] ZUFS - Zero-copy User-mode File System
Date: Fri, 2 Feb 2018 10:36:32 +0100	[thread overview]
Message-ID: <CAOssrKesx6bqq2ituZhTL8Aa6_gXiV0HUjXiAi1U-bcWFvoj3w@mail.gmail.com> (raw)
In-Reply-To: <05004066-1071-4244-3b6c-318b34f3f16b@netapp.com>

On Thu, Feb 1, 2018 at 7:59 PM, Boaz Harrosh <boazh@netapp.com> wrote:
> On 01/02/18 20:34, Chuck Lever wrote:
> <>
>> This work was also presented at the SNIA Persistent Memory Summit last week.
>> The use case of course is providing a user space platform for the development
>> and deployment of memory-based file systems. The value-add of this kind of
>> file system is ultra-low latency, which is a challenge for the current most
>> popular such framework, FUSE.

I can see the numbers being very impressive and very happy to see
progress being made in this field.

What I'd also really be interested to see is where those speedups come from.

As of linux-4.2/libfuse-3.0 there is a scalability improvement, that
can be enabled with the "-o clone_fd" option.  This option creates
per-thread queues, which are prerequisite to achieving full CPU/NUMA
affinity for request processing.   Even just turning of "clone_fd"
might improve the latency numbers for FUSE.

Thanks,
Miklos

  reply	other threads:[~2018-02-02  9:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 13:51 [LSF/MM TOPIC ATTEND][RFD] ZUFS - Zero-copy User-mode File System Boaz Harrosh
2018-02-01 18:34 ` Chuck Lever
2018-02-01 18:59   ` Boaz Harrosh
2018-02-02  9:36     ` Miklos Szeredi [this message]
2018-02-05 13:04       ` Boaz Harrosh
2018-02-05 15:48         ` Miklos Szeredi
2018-02-02 15:49     ` J. Bruce Fields
2018-02-02 16:09       ` Chuck Lever
2018-02-02 16:13         ` Bruce Fields
2018-02-09 17:47         ` Steve French
2018-02-05 12:53       ` Boaz Harrosh
2018-03-05 12:18     ` Greg KH

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=CAOssrKesx6bqq2ituZhTL8Aa6_gXiV0HUjXiAi1U-bcWFvoj3w@mail.gmail.com \
    --to=mszeredi@redhat.com \
    --cc=Amit.Golander@netapp.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=Shachar.Sharon@netapp.com \
    --cc=amir73il@gmail.com \
    --cc=andy.rudoff@intel.com \
    --cc=boazh@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=coughlan@redhat.com \
    --cc=jack@suse.cz \
    --cc=jmoyer@redhat.com \
    --cc=josef@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rwheeler@redhat.com \
    --cc=sagim@netapp.com \
    --cc=stephen@eideticom.com \
    --cc=sweil@redhat.com \
    --cc=swhiteho@redhat.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).