From: Kunwu Chan <chentao@kylinos.cn>
To: Dave Chinner <david@fromorbit.com>, kunwu.chan@linux.dev
Cc: chandan.babu@oracle.com, djwong@kernel.org,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: use KMEM_CACHE() to create xfs_defer_pending cache
Date: Fri, 1 Mar 2024 10:02:54 +0800 [thread overview]
Message-ID: <e7c115a1-a4cd-4fbd-ac54-2bd60a42dc87@kylinos.cn> (raw)
In-Reply-To: <ZeEStFZwMu068YTc@dread.disaster.area>
On 2024/3/1 07:26, Dave Chinner wrote:
> On Thu, Feb 29, 2024 at 04:33:42PM +0800, kunwu.chan@linux.dev wrote:
>> From: Kunwu Chan <chentao@kylinos.cn>
>>
>> Use the KMEM_CACHE() macro instead of kmem_cache_create() to simplify
>> the creation of SLAB caches when the default values are used.
>>
>> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
>> ---
>> fs/xfs/libxfs/xfs_defer.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/fs/xfs/libxfs/xfs_defer.c b/fs/xfs/libxfs/xfs_defer.c
>> index 66a17910d021..6d957fcc17f2 100644
>> --- a/fs/xfs/libxfs/xfs_defer.c
>> +++ b/fs/xfs/libxfs/xfs_defer.c
>> @@ -1143,9 +1143,7 @@ xfs_defer_resources_rele(
>> static inline int __init
>> xfs_defer_init_cache(void)
>> {
>> - xfs_defer_pending_cache = kmem_cache_create("xfs_defer_pending",
>> - sizeof(struct xfs_defer_pending),
>> - 0, 0, NULL);
>> + xfs_defer_pending_cache = KMEM_CACHE(xfs_defer_pending, 0);
>>
>> return xfs_defer_pending_cache != NULL ? 0 : -ENOMEM;
>> }
>
> Please stop wasting our time by trying to make changes that have
> already been rejected. I gave you good reasons last time for why we
> aren't going to make this change in XFS, and now you've forced
> Darrick to waste time repeating all those same reasons. You did not
> respond to my review comments last time, and now you are posting
> more patches that make the same rejected change.
>
Sorry for the bother. It's my bad.That reply email was probably
quarantined because of my mailbox server, and I just found it on the
quarantine list.
I'll stop from doing this. Apologies again for my interruption.
> PLease listen to the feedback you are given. Indeed, please respond
> and acknowledge that you have read and understood the feedback you
> have been given, otherwise I'll consider anything from this email
> address as "just another annoying bot" and killfile it.
Thank you very much for your detailed reply and explanation, I just saw
it, this patch is my problem, I forgot to check the previous mailing
list at the time.
Sorry again for the bad mood I have caused you.
>
> -Dave.
--
Thanks,
Kunwu
prev parent reply other threads:[~2024-03-01 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 8:33 [PATCH] xfs: use KMEM_CACHE() to create xfs_defer_pending cache kunwu.chan
2024-02-29 16:00 ` Darrick J. Wong
2024-02-29 23:26 ` Dave Chinner
2024-03-01 2:02 ` Kunwu Chan [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=e7c115a1-a4cd-4fbd-ac54-2bd60a42dc87@kylinos.cn \
--to=chentao@kylinos.cn \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=kunwu.chan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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 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.