From: "Paul E. McKenney" <paulmck@kernel.org>
To: urezki@gmail.com, joel@joelfernandes.org
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: What should we be doing to stress-test kfree_rcu()?
Date: Wed, 1 Apr 2020 11:44:15 -0700 [thread overview]
Message-ID: <20200401184415.GA7619@paulmck-ThinkPad-P72> (raw)
Hello!
What should we be doing to stress-test kfree_rcu(), including its ability
to cope with OOM conditions? Yes, rcuperf runs are nice, but they are not
currently doing much more than testing base functionality, performance,
and scalability.
Thanx, Paul
next reply other threads:[~2020-04-01 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 18:44 Paul E. McKenney [this message]
2020-04-01 20:50 ` What should we be doing to stress-test kfree_rcu()? Joel Fernandes
2020-04-01 21:16 ` Uladzislau Rezki
2020-04-01 21:24 ` Paul E. McKenney
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=20200401184415.GA7619@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rcu@vger.kernel.org \
--cc=urezki@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