All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "danielwa@cisco.com" <danielwa@cisco.com>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"nkela@cisco.com" <nkela@cisco.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"xe-linux-external@cisco.com" <xe-linux-external@cisco.com>
Subject: Re: [PATCH] jffs2: implement mount option to configure endianness
Date: Thu, 8 Nov 2018 07:25:30 -0800	[thread overview]
Message-ID: <20181108152530.GA27198@infradead.org> (raw)
In-Reply-To: <bee96cb5db73c325675881b180006e1382718abe.camel@infinera.com>

On Wed, Nov 07, 2018 at 06:41:47PM +0000, Joakim Tjernlund wrote:
> > Certainly not. I'm not sure which architectures do have Spectre V2
> > mitigations which make indirect branches expensive now... perhaps there is
> > no intersection with the cases where we really care about JFFS2 being
> > CPU-bound?
> 
> All that passing of a new extra arg and extra if .. elif .. does cost too.

I know of no current microarchitecture where an indirect call is cheaper
than a simple branch, which can be very well predicted.

  reply	other threads:[~2018-11-08 15:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 21:49 [PATCH] jffs2: implement mount option to configure endianness Nikunj Kela
2018-11-07  9:05 ` David Woodhouse
2018-11-07  9:16   ` Joakim Tjernlund
2018-11-07 16:12     ` David Woodhouse
2018-11-07 17:33       ` Daniel Walker
2018-11-07 17:58         ` David Woodhouse
2018-11-07 18:41           ` Joakim Tjernlund
2018-11-08 15:25             ` Christoph Hellwig [this message]
2018-11-07 19:21           ` Daniel Walker
2018-11-07 18:04   ` Nikunj Kela (nkela)
2018-11-07 18:14     ` Richard Weinberger
2018-11-08  8:11       ` David Woodhouse
2018-11-08 18:01         ` Nikunj Kela (nkela)
2018-11-08 18:50           ` Joakim Tjernlund
2018-11-08 19:47           ` David Woodhouse
2018-11-12 21:43             ` Daniel Walker
2018-11-12 22:50               ` Daniel Walker
2018-11-12 23:11                 ` David Woodhouse
2018-11-12 23:40                   ` Daniel Walker
2018-11-12 23:43                     ` David Woodhouse
2018-11-13  0:06                       ` Daniel Walker
2018-11-13 21:01                       ` Daniel Walker

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=20181108152530.GA27198@infradead.org \
    --to=hch@infradead.org \
    --cc=Joakim.Tjernlund@infinera.com \
    --cc=danielwa@cisco.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nkela@cisco.com \
    --cc=xe-linux-external@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.