From: Daniel Walker <danielwa@cisco.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: 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 09:33:03 -0800 [thread overview]
Message-ID: <20181107173303.slnb3i2d6ufaonp7@zorba> (raw)
In-Reply-To: <8b08e8b992093453bb2b9caff8cff08c.squirrel@twosheds.infradead.org>
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 ?
Daniel
next prev parent reply other threads:[~2018-11-07 17:33 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 [this message]
2018-11-07 17:58 ` David Woodhouse
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=20181107173303.slnb3i2d6ufaonp7@zorba \
--to=danielwa@cisco.com \
--cc=Joakim.Tjernlund@infinera.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.