All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Why are the MB/s of avx and raid6: twice as high for a docked ThinkPad than for an undocked ?
Date: Wed, 15 Jun 2016 23:46:34 +0200	[thread overview]
Message-ID: <5761CCBA.7050405@gmx.de> (raw)

This diff is reliable depending whether the T440s is docked (right) or not (left) :

Linux t44 4.5.7-hardened-r2 #1 SMP Wed Jun 15 23:39:10 CEST 2016 x86_64 Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz GenuineIntel GNU/Linux

215c215
<    avx       : 10196.000 MB/sec
---
>    avx       : 23504.000 MB/sec
225,234c225,234
< raid6: sse2x1   gen()  2578 MB/s
< raid6: sse2x1   xor()  2007 MB/s
< raid6: sse2x2   gen()  3246 MB/s
< raid6: sse2x2   xor()  2203 MB/s
< raid6: sse2x4   gen()  3773 MB/s
< raid6: sse2x4   xor()  2640 MB/s
< raid6: avx2x1   gen()  5042 MB/s
< raid6: avx2x2   gen()  5812 MB/s
< raid6: avx2x4   gen()  6824 MB/s
< raid6: using algorithm avx2x4 gen() 6824 MB/s
---
> raid6: sse2x1   gen()  5816 MB/s
> raid6: sse2x1   xor()  4515 MB/s
> raid6: sse2x2   gen()  7261 MB/s
> raid6: sse2x2   xor()  4968 MB/s
> raid6: sse2x4   gen()  8511 MB/s
> raid6: sse2x4   xor()  5916 MB/s
> raid6: avx2x1   gen() 11378 MB/s
> raid6: avx2x2   gen() 13117 MB/s
> raid6: avx2x4   gen() 15398 MB/s
> raid6: using algorithm avx2x4 gen() 15398 MB/s

And why do the units differ (MB/sec versus MB/s) ?

-- 
Toralf
PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7

             reply	other threads:[~2016-06-15 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 21:46 Toralf Förster [this message]
2016-06-16  9:14 ` Why are the MB/s of avx and raid6: twice as high for a docked ThinkPad than for an undocked ? Henrique de Moraes Holschuh
2016-06-16 10:16   ` Toralf Förster

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=5761CCBA.7050405@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.