Re: [PATCH] x86: Accelerate copy_page with non-temporal in X86

2021-04-13 Thread Kemeng Shi
tested. Also, it likely reduces unnecessary cache load and flush, and benifits the running processes which have data cached. -- Best wishes Kemeng Shi

Re:Re: [PATCH] x86: Accelerate copy_page with non-temporal in X86

2021-04-13 Thread Kemeng Shi
on 2021/4/13 19:01, Borislav Petkov wrote: > + linux-nvdimm > > Original mail at > https://lkml.kernel.org/r/3f28adee-8214-fa8e-b368-eaf8b1934...@huawei.com > > On Tue, Apr 13, 2021 at 02:25:58PM +0800, Kemeng Shi wrote: >> I'm using AEP with dax_kmem drvier, and

[PATCH] x86: Accelerate copy_page with non-temporal in X86

2021-04-12 Thread Kemeng Shi
None Logical Size: None Memory dimm topoloygy: AEP | DRAMDRAMDRAM | | | |---|---| CPU |---|---| | | | DRAMDRAMDRAM Signed-off-by: Kemeng Shi --- arch/x86/lib/copy_page_64.S | 73 -

[tip: sched/urgent] sched/core: Fix migration to invalid CPU in __set_cpus_allowed_ptr()

2019-09-27 Thread tip-bot2 for KeMeng Shi
The following commit has been merged into the sched/urgent branch of tip: Commit-ID: 714e501e16cd473538b609b3e351b2cc9f7f09ed Gitweb: https://git.kernel.org/tip/714e501e16cd473538b609b3e351b2cc9f7f09ed Author:KeMeng Shi AuthorDate:Mon, 16 Sep 2019 06:53:28 Committer

Re: Re: Re: [PATCH] connector: report comm change event when modifying /proc/pid/task/tid/comm

2019-09-18 Thread KeMeng Shi
On 2019/9/18 at 1:08, Will Deacon wrote: >On Tue, Sep 17, 2019 at 09:56:28AM -0400, KeMeng Shi wrote: >>on 2019/9/17 at 5:10, Will Deacon wrote: >>>The rough idea looks ok to me but I have two concerns: >>> >>> (1) This looks like it will be visible to user

Re: Re: [PATCH] connector: report comm change event when modifying /proc/pid/task/tid/comm

2019-09-17 Thread KeMeng Shi
rwise, put setting name and reporting event in crtical region may be the only answer. I'm sorry the response to (1) concern is missing in last mail. This is a full version. Apologize again for my mistake. Thanks for review. KeMeng Shi

Re: Re: [PATCH] connector: report comm change event when modifying /proc/pid/task/tid/comm

2019-09-16 Thread KeMeng Shi
There is no matter if user only care the latest comm change otherwise, put setting name and reporting event in crtical region may be the only answer. Thanks for review. KeMeng Shi

[PATCH] connector: report comm change event when modifying /proc/pid/task/tid/comm

2019-09-16 Thread KeMeng Shi
rovides a chance for application to monitor and control threads whose name is set by other threads. Signed-off-by: KeMeng Shi --- fs/proc/base.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/fs/proc/base.c b/fs/proc/base.c index ebea9501afb8..34ffe572ac69 100644 --- a/fs/proc/

[PATCH v2] sched: fix migration to invalid cpu in __set_cpus_allowed_ptr

2019-09-15 Thread KeMeng Shi
ces/system/cpu/cpu1/online" in turn. 3) Oops appears if the invalid cpu is set in memory after tested cpumask. Signed-off-by: KeMeng Shi Reviewed-by: Valentin Schneider --- Changes in v2: -solve format problems in log kernel/sched/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-