From: "David Woodhouse" <dwmw2@infradead.org>
To: "Daniel Walker" <danielwa@cisco.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Joakim Tjernlund" <joakim.tjernlund@infinera.com>,
"nkela@cisco.com" <nkela@cisco.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"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: Wed, 7 Nov 2018 17:58:53 -0000 [thread overview]
Message-ID: <df9cdf1753ec7e6e20c12aa096b98453.squirrel@twosheds.infradead.org> (raw)
In-Reply-To: <20181107173303.slnb3i2d6ufaonp7@zorba>
> On Wed, Nov 07, 2018 at 04:12:14PM -0000, David Woodhouse wrote:
>>
>> > Yes, this may slow things down. I am not sure I agree with the impl.
>> > either.
>> > Could one not make cpu_to_je_X/jeX_to_cpu a function ptr which is set
>> to
>> > a func. with the correct endian?
>>
>> On x86 retpoline would make that quite slow.
>
> Is x86 the largest consumer of jffs2 ?
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?
--
dwmw2
next prev parent reply other threads:[~2018-11-07 17:59 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 [this message]
2018-11-07 18:41 ` Joakim Tjernlund
2018-11-08 15:25 ` Christoph Hellwig
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=df9cdf1753ec7e6e20c12aa096b98453.squirrel@twosheds.infradead.org \
--to=dwmw2@infradead.org \
--cc=danielwa@cisco.com \
--cc=joakim.tjernlund@infinera.com \
--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 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).