From: bfields@fieldses.org (J. Bruce Fields)
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>,
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, 2 Feb 2018 10:49:52 -0500 [thread overview]
Message-ID: <20180202154952.GA3875@fieldses.org> (raw)
In-Reply-To: <05004066-1071-4244-3b6c-318b34f3f16b@netapp.com>
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.
> What about a different interface for a "trusted" binary with "Spectre
> mitigation" off. I know Redhat guys have a project where they want to
> sign and verify by Kernel all systemd /sbin/* binaries. If these
> binaries have such an hardened trust could we make them faster? (ie
> back to regular speed)
I don't think that helps.
--b.
next prev parent reply other threads:[~2018-02-02 15:49 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 [this message]
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=20180202154952.GA3875@fieldses.org \
--to=bfields@fieldses.org \
--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=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).