From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
colin.king@canonical.com, edumazet@google.com,
frextrite@gmail.com, jbi.octave@gmail.com,
joel@joelfernandes.org, madhuparnabhowmik04@gmail.com,
sjpark@amazon.de, urezki@gmail.com
Subject: Re: [GIT PULL v2 rcu/next] RCU commits for v5.7
Date: Tue, 24 Mar 2020 10:11:20 +0100 [thread overview]
Message-ID: <20200324091120.GB48322@gmail.com> (raw)
In-Reply-To: <20200322145310.GA7379@paulmck-ThinkPad-P72>
* Paul E. McKenney <paulmck@kernel.org> wrote:
> Hello, Ingo!
>
> As discussed off-list, my earlier RCU pull request contained a commit with
> KCSAN dependencies, which caused build failures in the absence of KCSAN.
> These dependencies went undetected due to a flaw in my testing process
> that erroneously included the KCSAN commits. This revised pull request
> removes those dependencies by pushing them to the post-v5.7 of the
> -rcu tree. Non-KCSAN builds are unaffected.
>
> As before, this pull request contains the following changes:
>
> 1. Documentation updates.
>
> https://lore.kernel.org/lkml/20200214233848.GA12744@paulmck-ThinkPad-P72
>
> 2. Miscellaneous fixes.
>
> https://lore.kernel.org/lkml/20200214235536.GA13364@paulmck-ThinkPad-P72
>
> 3. Make kfree_rcu() use kfree_bulk() for added performance.
>
> https://lore.kernel.org/lkml/20200215000031.GA14315@paulmck-ThinkPad-P72
>
> 4. Locking torture-test updates.
>
> https://lore.kernel.org/lkml/20200215000312.GA14585@paulmck-ThinkPad-P72
>
> 5. Callback-overload handling updates.
>
> https://lore.kernel.org/lkml/20200215001816.GA15284@paulmck-ThinkPad-P72
>
> 6. Tasks-RCU KCSAN and sparse updates.
>
> https://lore.kernel.org/lkml/20200215002446.GA15663@paulmck-ThinkPad-P72
>
> 7. SRCU updates.
>
> https://lore.kernel.org/lkml/20200215002907.GA15895@paulmck-ThinkPad-P72
>
> 8. Torture-test updates.
>
> https://lore.kernel.org/lkml/20200215003634.GA16227@paulmck-ThinkPad-P72
>
> All of these have been subjected to the kbuild test robot testing,
> will get -next testing in the next -next, and are available in the git
> repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
>
> for you to fetch changes up to aa93ec620be378cce1454286122915533ff8fa48:
>
> Merge branches 'doc.2020.02.27a', 'fixes.2020.03.21a', 'kfree_rcu.2020.02.20a', 'locktorture.2020.02.20a', 'ovld.2020.02.20a', 'rcu-tasks.2020.02.20a', 'srcu.2020.02.20a' and 'torture.2020.02.20a' into HEAD (2020-03-21 17:15:11 -0700)
>
> There is a modest increase in code size of about 700 lines. About 300
> of these added lines were documentation, almost 200 more from adding
> kfree_bulk() support to kfree_rcu(), about 150 from torture-test
> improvements, and about 80 lines from improved callback-overload handling.
> All in all, good value from this expansion.
> 34 files changed, 1015 insertions(+), 294 deletions(-)
Pulled, thanks a lot Paul!
Ingo
prev parent reply other threads:[~2020-03-24 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 21:10 [GIT PULL rcu/next] RCU commits for v5.7 Paul E. McKenney
2020-03-22 14:53 ` [GIT PULL v2 " Paul E. McKenney
2020-03-24 9:11 ` Ingo Molnar [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=20200324091120.GB48322@gmail.com \
--to=mingo@kernel.org \
--cc=colin.king@canonical.com \
--cc=edumazet@google.com \
--cc=frextrite@gmail.com \
--cc=jbi.octave@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik04@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=sjpark@amazon.de \
--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;
as well as URLs for NNTP newsgroup(s).