From: Khazhismel Kumykov <khazhy@google.com>
To: miklos@szeredi.hu
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Shakeel Butt <shakeelb@google.com>
Subject: Re: [PATCH v2 1/3] fuse: on 64-bit store time in d_fsdata directly
Date: Tue, 3 Sep 2019 14:08:07 -0700 [thread overview]
Message-ID: <CACGdZYKPyBnJvZWY7+JiUoHZvzC+RWonbZ1PBKtpCXCa4BVa6w@mail.gmail.com> (raw)
In-Reply-To: <20190822200030.141272-1-khazhy@google.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
On Thu, Aug 22, 2019 at 1:00 PM Khazhismel Kumykov <khazhy@google.com> wrote:
>
> Implements the optimization noted in f75fdf22b0a8 ("fuse: don't use
> ->d_time"), as the additional memory can be significant. (In particular,
> on SLAB configurations this 8-byte alloc becomes 32 bytes). Per-dentry,
> this can consume significant memory.
>
> Reviewed-by: Shakeel Butt <shakeelb@google.com>
> Signed-off-by: Khazhismel Kumykov <khazhy@google.com>
> ---
> fs/fuse/dir.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
ping?
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4843 bytes --]
prev parent reply other threads:[~2019-09-03 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 20:00 [PATCH v2 1/3] fuse: on 64-bit store time in d_fsdata directly Khazhismel Kumykov
2019-08-22 20:00 ` [PATCH v2 2/3] fuse: pass gfp flags to fuse_request_alloc Khazhismel Kumykov
2019-08-22 21:42 ` Shakeel Butt
2019-08-22 20:00 ` [PATCH v2 3/3] fuse: kmemcg account fs data Khazhismel Kumykov
2019-08-22 21:43 ` Shakeel Butt
2019-09-03 21:08 ` Khazhismel Kumykov [this message]
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=CACGdZYKPyBnJvZWY7+JiUoHZvzC+RWonbZ1PBKtpCXCa4BVa6w@mail.gmail.com \
--to=khazhy@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=shakeelb@google.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).