From: Chao Yu <chao@kernel.org>
To: Wu Bo <bo.wu@vivo.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, wubo.oduw@gmail.com
Subject: Re: [PATCH 1/1] f2fs: allocate trace path buffer from names_cache
Date: Tue, 18 Apr 2023 23:51:02 +0800 [thread overview]
Message-ID: <e2ec7e19-634c-a065-fe7a-b052d02d4752@kernel.org> (raw)
In-Reply-To: <20230414104308.6591-1-bo.wu@vivo.com>
On 2023/4/14 18:43, Wu Bo wrote:
> It would be better to use the dedicated slab to store path.
>
> Signed-off-by: Wu Bo <bo.wu@vivo.com>
> ---
> fs/f2fs/file.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 15dabeac4690..27137873958f 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -4361,7 +4361,7 @@ static void f2fs_trace_rw_file_path(struct kiocb *iocb, size_t count, int rw)
> struct inode *inode = file_inode(iocb->ki_filp);
> char *buf, *path;
>
> - buf = f2fs_kmalloc(F2FS_I_SB(inode), PATH_MAX, GFP_KERNEL);
> + buf = __getname();
How about:
buf = f2fs_kmem_cache_alloc(names_cachep, GFP_KERNEL, NULL, F2FS_I_SB(inode));
> if (!buf)
> return;
> path = dentry_path_raw(file_dentry(iocb->ki_filp), buf, PATH_MAX);
> @@ -4374,7 +4374,7 @@ static void f2fs_trace_rw_file_path(struct kiocb *iocb, size_t count, int rw)
> trace_f2fs_dataread_start(inode, iocb->ki_pos, count,
> current->pid, path, current->comm);
> free_buf:
> - kfree(buf);
> + __putname(buf);
kmem_cache_free(names_cachep, buf);
Thanks,
> }
>
> static ssize_t f2fs_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
next prev parent reply other threads:[~2023-04-18 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 10:43 [PATCH 1/1] f2fs: allocate trace path buffer from names_cache Wu Bo
2023-04-18 15:51 ` Chao Yu [this message]
2023-04-18 16:07 ` Jaegeuk Kim
2023-04-19 6:28 ` Chao Yu
2023-04-19 18:18 ` Jaegeuk Kim
2023-04-19 19:45 ` [f2fs-dev] " Jaegeuk Kim
2023-04-20 1:10 ` Chao Yu
2023-04-19 1:32 ` Wu Bo
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=e2ec7e19-634c-a065-fe7a-b052d02d4752@kernel.org \
--to=chao@kernel.org \
--cc=bo.wu@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wubo.oduw@gmail.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