From: Sven Van Asbroeck <thesven73@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Deepa Dinamani <deepa.kernel@gmail.com>,
David Howells <dhowells@redhat.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Janos Farkas <chexum+dev@gmail.com>,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH v1 0/2] address romfs performance regression
Date: Mon, 22 Jun 2020 20:45:18 -0400 [thread overview]
Message-ID: <20200623004520.26520-1-TheSven73@gmail.com> (raw)
Tree: next-20200613
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: David Howells <dhowells@redhat.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Janos Farkas <chexum+dev@gmail.com>
Cc: Jeff Layton <jlayton@kernel.org>
To: linux-kernel@vger.kernel.org
Sven Van Asbroeck (2):
romfs: use s_blocksize(_bits) if CONFIG_BLOCK
romfs: address performance regression since v3.10
fs/romfs/storage.c | 25 ++++++++--------
fs/romfs/super.c | 71 ++++++++++++++++++++++++++++++++++++++++++----
2 files changed, 78 insertions(+), 18 deletions(-)
--
2.17.1
next reply other threads:[~2020-06-23 0:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 0:45 Sven Van Asbroeck [this message]
2020-06-23 0:45 ` [PATCH v1 1/2] romfs: use s_blocksize(_bits) if CONFIG_BLOCK Sven Van Asbroeck
2020-06-23 0:45 ` [PATCH v1 2/2] romfs: address performance regression since v3.10 Sven Van Asbroeck
2020-06-23 16:16 ` kernel test robot
2020-06-23 16:16 ` kernel test robot
2020-06-23 17:05 ` Sven Van Asbroeck
2020-07-09 12:16 ` Sven Van Asbroeck
-- strict thread matches above, loose matches on Subject: below --
2020-06-23 0:42 [PATCH v1 0/2] address romfs performance regression Sven Van Asbroeck
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=20200623004520.26520-1-TheSven73@gmail.com \
--to=thesven73@gmail.com \
--cc=chexum+dev@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=deepa.kernel@gmail.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.