From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Alex Zhuravlev <azhuravlev@whamcloud.com>
Cc: "Благодаренко Артём" <artem.blagodarenko@gmail.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext4: mballoc - prefetching for bitmaps
Date: Fri, 19 Jun 2020 13:16:41 -0400 [thread overview]
Message-ID: <20200619171641.GA3963397@mit.edu> (raw)
In-Reply-To: <895DB4D0-0F00-4467-A87F-33222443615A@whamcloud.com>
On Sat, May 30, 2020 at 05:01:40AM +0000, Alex Zhuravlev wrote:
>
> Hi
>
> > On 29 May 2020, at 19:19, Благодаренко Артём <artem.blagodarenko@gmail.com> wrote:
> >
> > Also, we have encountered directory creating rate drop with this (not exact this, but Lustre FS version) patch. From 70-80K to 30-40K.
> > Excluding this patch restore rates to the original values.
> > I am investigating it now. Alex, do you expect this optimisation has impact to names creation?
> > Is plenty of files and directories creation corner case for this optimisation?
>
> Noticed as well, the last version posted to the list should have this problem fixed.
I'm not seeing any newer version of this patch since the one on this
thread, posted on May 15th.
Am I missing something? What's the latest version of this patch that you have?
- Ted
next prev parent reply other threads:[~2020-06-19 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 10:07 [PATCH 1/2] ext4: mballoc - prefetching for bitmaps Alex Zhuravlev
2020-05-20 4:45 ` kbuild test robot
2020-05-23 19:27 ` kbuild test robot
2020-05-28 14:47 ` Theodore Y. Ts'o
2020-05-30 4:57 ` Alex Zhuravlev
2020-05-29 16:19 ` Благодаренко Артём
2020-05-30 5:01 ` Alex Zhuravlev
2020-06-19 17:16 ` Theodore Y. Ts'o [this message]
2020-06-19 18:23 ` Alex Zhuravlev
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=20200619171641.GA3963397@mit.edu \
--to=tytso@mit.edu \
--cc=artem.blagodarenko@gmail.com \
--cc=azhuravlev@whamcloud.com \
--cc=linux-ext4@vger.kernel.org \
/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).