From: Ju Hyung Park <qkrwngud825@gmail.com>
To: Chao Yu <yuchao0@huawei.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use kmem_cache pool during xattr lookups
Date: Mon, 29 Jul 2019 16:48:35 +0900 [thread overview]
Message-ID: <CAD14+f3ZGaY5jM+A5Bv=cSZNUeYaY=hywaG44SsotMNVz=D09g@mail.gmail.com> (raw)
In-Reply-To: <24f7940d-325c-c2b3-608e-ce311db2dc7d@huawei.com>
Hi Chao and Jaegeuk,
I have no idea how that patch got merged.
We(me and Yaro) were supposed to work on doing some finishing touches
to the patch before sending it to upstream.
I'll personally check with Yaro.
Jaegeuk, please remove the patch.
That patch has numerous issues, biggest one being hardcoded size(SZ_256).
Also, I need to figure out how to allocate kmem cache per mounts.
Thanks.
On Mon, Jul 29, 2019 at 4:28 PM Chao Yu <yuchao0@huawei.com> wrote:
>
> Hi Jaegeuk, Ju Hyung, Yaroslav,
>
> I can see "f2fs: xattr: reserve cache for xattr allocations" has been merged in
> dev-test branch, however, it doesn't exist in f2fs mailing list, so I can not
> comment on it.... Can anyone send it to the list?
>
> Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-07-29 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 15:06 [f2fs-dev] [PATCH] f2fs: use kmem_cache pool during xattr lookups Park Ju Hyung
2019-07-11 15:13 ` Ju Hyung Park
2019-07-11 17:06 ` Jaegeuk Kim
2019-07-12 7:46 ` Chao Yu
2019-07-29 7:27 ` Chao Yu
2019-07-29 7:48 ` Ju Hyung Park [this message]
2019-07-29 8:25 ` Chao Yu
2019-07-30 18:05 ` Jaegeuk Kim
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='CAD14+f3ZGaY5jM+A5Bv=cSZNUeYaY=hywaG44SsotMNVz=D09g@mail.gmail.com' \
--to=qkrwngud825@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.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).