linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <openosd@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
	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: Mon, 5 Feb 2018 14:53:01 +0200	[thread overview]
Message-ID: <cafcfe95-1c39-f781-6594-4179793726f3@gmail.com> (raw)
In-Reply-To: <20180202154952.GA3875@fieldses.org>

On 02/02/18 17:49, J. Bruce Fields wrote:
<>
>> 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.
> 

If that does not help then I'm clueless. I understood that the
slowdown is because some CPU pipelines need stalling (flushing)
because back-from-kernel call in usermode can (theoretically)
inspect the other side of the un-taken speculated branch .....
So if I trust the user-mode app I can trust it will not misuse
that info?

But again I'm completely clueless. What else then "app trust"
can there be?

> --b.
> 

Thanks
Boaz

  parent reply	other threads:[~2018-02-05 12:53 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
2018-02-05 12:53       ` Boaz Harrosh [this message]
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=cafcfe95-1c39-f781-6594-4179793726f3@gmail.com \
    --to=openosd@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).