Re: [RFC PATCH] alispinlock: acceleration from lock integration on multi-core platform

From	Ling Ma <ling.ma.program@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [RFC PATCH] alispinlock: acceleration from lock integration on multi-core platform
Date	2016-04-11 10:10 +0200
Message-ID	<rmF51-2CR-27@gated-at.bofh.it> (permalink)
References	(9 earlier) <qSAiS-5me-27@gated-at.bofh.it> <qSGxY-1lu-19@gated-at.bofh.it> <qXXya-5xy-1@gated-at.bofh.it> <qYdtg-7qy-13@gated-at.bofh.it> <rkqa6-5dS-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Is it acceptable for performance improvement or more comments on this patch?

Thanks
Ling

2016-04-05 11:44 GMT+08:00 Ling Ma <ling.ma.program@gmail.com>:
> Hi Longman,
>
>> with some modest increase in performance. That can be hard to justify. Maybe
>> you should find other use cases that involve less changes, but still have
>> noticeable performance improvement. That will make it easier to be accepted.
>
> The attachment is for other use case with the new lock optimization.
> It include two files: main.c (user space workload),
> fcntl-lock-opt.patch (kernel patch on 4.3.0-rc4 version)
> (The hardware platform is on Intel E5 2699 V3, 72 threads (18core *2Socket *2HT)
>
> 1. when we run a.out from main.c on original 4.3.0-rc4 version,
> the average throughput from a.out is 1887592( 98% cpu cost from perf top -d1)
>
> 2. when we run a.out from main.c with the fcntl-lock-opt.patch ,
> the average throughput from a.out is 5277281 (91% cpu cost from perf top -d1)
>
> So we say the new mechanism give us about 2.79x (5277281 / 1887592) improvement.
>
> Appreciate your comments.
>
> Thanks
> Ling

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [RFC PATCH] alispinlock: acceleration from lock integration on  multi-core platform Ling Ma <ling.ma.program@gmail.com> - 2016-04-11 10:10 +0200

csiph-web