Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1457823 > unrolled thread

Re: [RFC PATCH 3/4] Make deadline max-heap faster avoiding real swaps on heapify ops.

Started byPeter Zijlstra <peterz@infradead.org>
First post2016-08-08 16:10 +0200
Last post2016-08-08 16:10 +0200
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.


Contents

  Re: [RFC PATCH 3/4] Make deadline max-heap faster avoiding real  swaps on heapify ops. Peter Zijlstra <peterz@infradead.org> - 2016-08-08 16:10 +0200

#1457823 — Re: [RFC PATCH 3/4] Make deadline max-heap faster avoiding real swaps on heapify ops.

FromPeter Zijlstra <peterz@infradead.org>
Date2016-08-08 16:10 +0200
SubjectRe: [RFC PATCH 3/4] Make deadline max-heap faster avoiding real swaps on heapify ops.
Message-ID<s3TpD-2p3-23@gated-at.bofh.it>
On Tue, Jul 19, 2016 at 11:44:52AM +0200, Tommaso Cucinotta wrote:
> This change achieves up to 10% of speed-up for cpudl_set() calls, as
> measured with a andomly generated workload of 1K,10K,100K random heap
> insertions and deletions (75% cpudl_set() calls with is_valid=1 and
> 25% with is_valid=0), and randomly generated cpu IDs, with up to 256
> CPUs, as measured on an Intel Core2 Duo.

Changelog fails to explain _what_ the change is.

Some details on the change in implementation and why this is faster
would be good.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web