linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Zhou <dennis@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@linux.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] percpu changes for v5.3-rc1
Date: Sat, 13 Jul 2019 00:17:33 -0400	[thread overview]
Message-ID: <20190713041733.GA80860@dennisz-mbp.dhcp.thefacebook.com> (raw)

Hi Linus,

This pull request includes changes to let percpu_ref release the backing
percpu memory earlier after it has been switched to atomic in cases
where the percpu ref is not revived. This will help recycle percpu
memory earlier in cases where the refcounts are pinned for prolonged
periods of time.

Thanks,
Dennis

The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:

  Linux 5.1 (2019-05-05 17:42:58 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu.git for-5.3

for you to fetch changes up to 7d9ab9b6adffd9c474c1274acb5f6208f9a09cf3:

  percpu_ref: release percpu memory early without PERCPU_REF_ALLOW_REINIT (2019-05-09 10:51:06 -0700)

----------------------------------------------------------------
Roman Gushchin (4):
      percpu_ref: introduce PERCPU_REF_ALLOW_REINIT flag
      io_uring: initialize percpu refcounters using PERCU_REF_ALLOW_REINIT
      md: initialize percpu refcounters using PERCU_REF_ALLOW_REINIT
      percpu_ref: release percpu memory early without PERCPU_REF_ALLOW_REINIT

 drivers/md/md.c                 |  3 ++-
 fs/io_uring.c                   |  3 ++-
 include/linux/percpu-refcount.h | 10 +++++++++-
 lib/percpu-refcount.c           | 13 +++++++++++--
 4 files changed, 24 insertions(+), 5 deletions(-)


             reply	other threads:[~2019-07-13  4:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13  4:17 Dennis Zhou [this message]
2019-07-15  0:30 ` [GIT PULL] percpu changes for v5.3-rc1 pr-tracker-bot

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=20190713041733.GA80860@dennisz-mbp.dhcp.thefacebook.com \
    --to=dennis@kernel.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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 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).