From: Richard Weinberger <richard.weinberger@gmail.com>
To: nkela@cisco.com
Cc: David Woodhouse <dwmw2@infradead.org>,
"linux-mtd @ lists . infradead . org"
<linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
xe-linux-external@cisco.com
Subject: Re: [PATCH] jffs2: implement mount option to configure endianness
Date: Wed, 7 Nov 2018 19:14:20 +0100 [thread overview]
Message-ID: <CAFLxGvz8QgK1P6d-_biSRk4fyYEobio315_tUP+cRXTvt+m1hA@mail.gmail.com> (raw)
In-Reply-To: <591D4732-BC3E-4F85-9277-25E049FFF4BA@cisco.com>
On Wed, Nov 7, 2018 at 7:05 PM Nikunj Kela (nkela) <nkela@cisco.com> wrote:
> I had tried to use configs to start with via the following patch however I was advised to have a mount option:
> http://lists.infradead.org/pipermail/linux-mtd/2018-November/085126.html
Just show performance numbers on how your implementation has an impact or not.
So far your implementation is also not much optimized, maybe likely()
or static keys can help...
--
Thanks,
//richard
next prev parent reply other threads:[~2018-11-07 18:14 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
2018-11-07 19:21 ` Daniel Walker
2018-11-07 18:04 ` Nikunj Kela (nkela)
2018-11-07 18:14 ` Richard Weinberger [this message]
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=CAFLxGvz8QgK1P6d-_biSRk4fyYEobio315_tUP+cRXTvt+m1hA@mail.gmail.com \
--to=richard.weinberger@gmail.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 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).