All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: Huangzhaoyang <huangzhaoyang@gmail.com>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	cluster-devel@redhat.com,
	Zhaoyang Huang <zhaoyang.huang@unisoc.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs: amend SLAB_RECLAIM_ACCOUNT on gfs2 related slab cache
Date: Tue, 5 Jan 2021 07:54:34 -0500 (EST)	[thread overview]
Message-ID: <1535117686.42500348.1609851274846.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1609807642-31552-1-git-send-email-huangzhaoyang@gmail.com>

----- Original Message -----
> From: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
> 
> As gfs2_quotad_cachep and gfs2_glock_cachep have registered
> the shrinker, amending SLAB_RECLAIM_ACCOUNT when creating
> them, which make the slab acount to be presiced.
> 
> Signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
> ---
> v2: add gfs2_glock_cachep for same operation
> ---
Hi,

Thanks. Your patch is now pushed to the linux-gfs2/for-next branch.
I cleaned up the description a bit. For example, I changed "fs:" to
"gfs2:" to conform to other gfs2 patches.

Regards,

Bob Peterson


WARNING: multiple messages have this Message-ID (diff)
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v2] fs: amend SLAB_RECLAIM_ACCOUNT on gfs2 related slab cache
Date: Tue, 5 Jan 2021 07:54:34 -0500 (EST)	[thread overview]
Message-ID: <1535117686.42500348.1609851274846.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1609807642-31552-1-git-send-email-huangzhaoyang@gmail.com>

----- Original Message -----
> From: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
> 
> As gfs2_quotad_cachep and gfs2_glock_cachep have registered
> the shrinker, amending SLAB_RECLAIM_ACCOUNT when creating
> them, which make the slab acount to be presiced.
> 
> Signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
> ---
> v2: add gfs2_glock_cachep for same operation
> ---
Hi,

Thanks. Your patch is now pushed to the linux-gfs2/for-next branch.
I cleaned up the description a bit. For example, I changed "fs:" to
"gfs2:" to conform to other gfs2 patches.

Regards,

Bob Peterson



  reply	other threads:[~2021-01-05 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05  0:47 [PATCH v2] fs: amend SLAB_RECLAIM_ACCOUNT on gfs2 related slab cache Huangzhaoyang
2021-01-05  0:47 ` [Cluster-devel] " Huangzhaoyang
2021-01-05 12:54 ` Bob Peterson [this message]
2021-01-05 12:54   ` Bob Peterson
2021-01-05 21:07   ` Andreas Grünbacher
2021-01-05 21:07     ` [Cluster-devel] " Andreas Grünbacher

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=1535117686.42500348.1609851274846.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=agruenba@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=huangzhaoyang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhaoyang.huang@unisoc.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 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.