From: Hanjun Guo <guohanjun@huawei.com>
To: Will Deacon <will@kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Kees Cook <keescook@chromium.org>, Ingo Molnar <mingo@kernel.org>,
"Elena Reshetova" <elena.reshetova@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [RESEND PATCH v4 00/10] Rework REFCOUNT_FULL using atomic_fetch_* operations
Date: Fri, 22 Nov 2019 11:44:55 +0800 [thread overview]
Message-ID: <2d008348-e000-0627-132f-7fc8990de3a4@huawei.com> (raw)
In-Reply-To: <20191121115902.2551-1-will@kernel.org>
On 2019/11/21 19:58, Will Deacon wrote:
> Hi everybody,
>
> This is a resend of version four of the patches I posted here:
>
> v4: https://lore.kernel.org/lkml/20191030143035.19440-1-will@kernel.org
>
> Previous versions can be found at:
>
> v1: https://lkml.kernel.org/r/20190802101000.12958-1-will@kernel.org
> v2: https://lkml.kernel.org/r/20190827163204.29903-1-will@kernel.org
> v3: https://lkml.kernel.org/r/20191007154703.5574-1-will@kernel.org
>
> I didn't receive any feedback last time around, other than some positive
> noises from Kees, so please consider this for inclusion in mainline.
This time I tested this patch set on both ARM64 and x86 server, against
5.4-rc8.
On ARM64, similar test case and the similar performance improvement.
On X86, I tested on a 24 cores Xeon(R) CPU E5-2620, with kernel compile
(make -j) for test case, and no issue was found.
Tested-by: Hanjun Guo <guohanjun@huawei.com>
Thanks
Hanjun
prev parent reply other threads:[~2019-11-22 3:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 11:58 Will Deacon
2019-11-21 11:58 ` [RESEND PATCH v4 01/10] lib/refcount: Define constants for saturation and max refcount values Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2019-11-21 11:58 ` [RESEND PATCH v4 02/10] lib/refcount: Ensure integer operands are treated as signed Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2019-11-21 11:58 ` [RESEND PATCH v4 03/10] lib/refcount: Remove unused refcount_*_checked() variants Will Deacon
2019-11-21 14:55 ` David Sterba
2019-11-21 17:11 ` Kees Cook
2019-11-21 17:17 ` David Sterba
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2019-11-21 11:58 ` [RESEND PATCH v4 04/10] lib/refcount: Move bulk of REFCOUNT_FULL implementation into header Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: Move the bulk of the REFCOUNT_FULL implementation into the <linux/refcount.h> header tip-bot2 for Will Deacon
2019-11-21 11:58 ` [RESEND PATCH v4 05/10] lib/refcount: Improve performance of generic REFCOUNT_FULL code Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2020-02-26 4:10 ` [RESEND PATCH v4 05/10] lib/refcount: " Jann Horn
2020-02-28 10:43 ` Will Deacon
2020-03-02 13:06 ` Jann Horn
2019-11-21 11:58 ` [RESEND PATCH v4 06/10] lib/refcount: Move saturation warnings out of line Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2019-11-21 11:58 ` [RESEND PATCH v4 07/10] lib/refcount: Consolidate REFCOUNT_{MAX,SATURATED} definitions Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2019-11-21 11:59 ` [RESEND PATCH v4 08/10] refcount: Consolidate implementations of refcount_t Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2019-12-01 15:49 ` [refcount] d2d337b185: WARNING:at_lib/refcount.c:#refcount_warn_saturate kernel test robot
2019-12-02 9:43 ` Ard Biesheuvel
2019-12-03 8:01 ` [LKP] " Rong Chen
2019-12-03 8:09 ` Will Deacon
2019-12-03 8:42 ` Rong Chen
2019-11-21 11:59 ` [RESEND PATCH v4 09/10] lib/refcount: Remove unused 'refcount_error_report()' function Will Deacon
2019-11-25 8:19 ` [tip: locking/core] locking/refcount: " tip-bot2 for Will Deacon
2019-11-21 11:59 ` [RESEND PATCH v4 10/10] drivers/lkdtm: Remove references to CONFIG_REFCOUNT_FULL Will Deacon
2019-11-25 8:19 ` [tip: locking/core] lkdtm: " tip-bot2 for Will Deacon
2019-11-21 12:07 ` [RESEND PATCH v4 00/10] Rework REFCOUNT_FULL using atomic_fetch_* operations Ard Biesheuvel
2019-11-22 3:44 ` Hanjun Guo [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=2d008348-e000-0627-132f-7fc8990de3a4@huawei.com \
--to=guohanjun@huawei.com \
--cc=ard.biesheuvel@linaro.org \
--cc=elena.reshetova@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome