public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Intel(R) C600 SAS Controller
Date: Wed, 11 Jun 2014 12:52:27 +0100	[thread overview]
Message-ID: <539842FB.9050907@thegeezer.net> (raw)
In-Reply-To: <53983BD2.60104@xunil.at>

On 06/11/2014 12:21 PM, Stefan G. Weichinger wrote:
> Am 11.06.2014 13:18, schrieb thegeezer:
>
>> just out of curiosity, what happens if you do # dd 
>> if=/dev/vg01/amhold of=/dev/null bs=1M count=100 # dd if=/dev/sdc 
>> of=/dev/null bs=1M count=100
>
>
> booze ~ # dd if=/dev/vg01/amhold of=/dev/null bs=1M count=100
> 100+0 Datensätze ein
> 100+0 Datensätze aus
> 104857600 Bytes (105 MB) kopiert, 1,71368 s, 61,2 MB/s
>
> booze ~ # dd if=/dev/sdc of=/dev/null bs=1M count=100
> 100+0 Datensätze ein
> 100+0 Datensätze aus
> 104857600 Bytes (105 MB) kopiert, 2,40518 s, 43,6 MB/s
>
>

ok baffling.
sdc i already said would be slower but not this much slower
it certainly should not be slower than the lvm that sits on top of it!
i can't see anything in the cgroups that stands out, maybe someone else
can give a better voice to this.

all i can think is there is other IO happening
in atop if you can highlight any line that begins LVM CPU or DSK and
paste it in to a reply - with no virtualmachines running and no dd or
anything.
then run a dd as before and highlight the lines in atop while it is
running (maybe increase count to 1000 to give yourself a chance) and
paste in here too




  reply	other threads:[~2014-06-11 11:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  7:52 [gentoo-user] Intel(R) C600 SAS Controller Stefan G. Weichinger
2014-05-24 19:24 ` Stefan G. Weichinger
2014-05-26 17:47   ` Stefan G. Weichinger
2014-05-26 19:57     ` Stefan G. Weichinger
2014-05-27 13:03       ` Stefan G. Weichinger
2014-06-10 19:57         ` Stefan G. Weichinger
2014-06-10 20:02           ` Stefan G. Weichinger
2014-06-10 22:27             ` Stefan G. Weichinger
2014-06-11  8:47               ` Stefan G. Weichinger
2014-06-11  9:19         ` thegeezer
2014-06-11  9:34           ` Stefan G. Weichinger
2014-06-11 10:14             ` thegeezer
2014-06-11 10:27               ` thegeezer
2014-06-11 10:34               ` Stefan G. Weichinger
2014-06-11 10:41                 ` thegeezer
2014-06-11 10:49                   ` Stefan G. Weichinger
2014-06-11 11:01                     ` thegeezer
2014-06-11 11:20                       ` Stefan G. Weichinger
2014-06-11 11:18                     ` thegeezer
2014-06-11 11:21                       ` Stefan G. Weichinger
2014-06-11 11:52                         ` thegeezer [this message]
2014-06-11 12:41                           ` Stefan G. Weichinger
2014-06-11 13:32                             ` thegeezer
2014-06-11 13:44                               ` Stefan G. Weichinger
2014-06-11 14:15                                 ` Stefan G. Weichinger
2014-06-11 14:18                                   ` thegeezer
2014-06-11 14:38                                     ` Stefan G. Weichinger
2014-06-11 18:57                                       ` Stefan G. Weichinger
2014-06-11 20:17                                         ` thegeezer
2014-06-12  8:15                                           ` Stefan G. Weichinger

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=539842FB.9050907@thegeezer.net \
    --to=thegeezer@thegeezer.net \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox