Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1262266 > unrolled thread
| Started by | Ling Ma <ling.ma.program@gmail.com> |
|---|---|
| First post | 2015-11-04 13:50 +0100 |
| Last post | 2015-11-04 13:50 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Improve spinlock performance by moving work to one core Ling Ma <ling.ma.program@gmail.com> - 2015-11-04 13:50 +0100
| From | Ling Ma <ling.ma.program@gmail.com> |
|---|---|
| Date | 2015-11-04 13:50 +0100 |
| Subject | Re: Improve spinlock performance by moving work to one core |
| Message-ID | <qr5FM-tl-17@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi All, (send again for linux-kernel@vger.kernel.org) Spinlock caused cache line ping-pong between cores, we have to spend lots of time to get serialized execution. However if we present the serialized work to one core, it will help us save much time. In the attachment we changed code based on queued spinlock The data tell us the spinlock performance can be improved by over 2X on 68cores over 3X on 2 cores (Intel 2699v3 2 sockets, COD off, HT on) In the following time we will try to send out the formal patch Appreciate your comments. Thanks
Back to top | Article view | linux.kernel
csiph-web