linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Bruce Fields <bfields@fieldses.org>,
	Boaz Harrosh <boazh@netapp.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>,
	coughlan@redhat.com, Jeff Moyer <jmoyer@redhat.com>,
	Sage Weil <sweil@redhat.com>,
	Miklos Szeredi <mszeredi@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, 9 Feb 2018 11:47:57 -0600	[thread overview]
Message-ID: <CAH2r5mv6QPvEe1Py+yLFBd-Ysasbk+QXTMqMWt+GmhVK_onD6g@mail.gmail.com> (raw)
In-Reply-To: <446CAE69-36E0-4F72-85C3-2DCC60B489B6@oracle.com>

On Fri, Feb 2, 2018 at 10:09 AM, Chuck Lever <chuck.lever@oracle.com> wrote:
>
>
>> On Feb 2, 2018, at 10:49 AM, bfields@fieldses.org wrote:
>>
>> On Thu, Feb 01, 2018 at 08:59:18PM +0200, Boaz Harrosh 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.
>>>>
>>>> To start, I can think of three areas where specific questions might
>>>> be entertained by LSF/MM attendees:
>>>>
>>>> - Spectre mitigations make this whole "user space filesystem"
>>>> arrangement even slower, thanks to additional context switches
>>>> between user space and the kernel.
>>
>> I think you're referring to the KPTI patches, which address Meltdown,
>> not Spectre.
>
> I enabled KPTI on my NFS client and server systems in early
> v4.15-rc, and didn't measure a change in latency or throughput.
>
> But with v4.15 final, which includes some Spectre mitigations,
> write(2) on NFS files, for example, takes about 15us longer.
> Since the RPC round-trip times did not increase, I presume this
> extra latency is incurred on the client, where the user-kernel
> boundary transitions occur.
>
> <shrug>

That is interesting data.

A loosely related question is whether ZUFS would be helpful in
a typical NFS or SMB3 scenario (under the server) - especially
with low latency RDMA (SMB3 Direct) connection to the server
(in the case of SMB3, we would want to consider what this would
look like with i/o from the same client, potentially the same file,
coming in on multiple RDMA cards ).

-- 
Thanks,

Steve

  parent reply	other threads:[~2018-02-09 17:48 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
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 [this message]
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=CAH2r5mv6QPvEe1Py+yLFBd-Ysasbk+QXTMqMWt+GmhVK_onD6g@mail.gmail.com \
    --to=smfrench@gmail.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=bfields@fieldses.org \
    --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=mszeredi@redhat.com \
    --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).