All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuri Tikhonov <yur@emcraft.com>
To: Cheng Renquan <crquan@gmail.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	linux-raid@vger.kernel.org, linuxppc-dev@ozlabs.org, dzu@denx.de,
	wd@denx.de, yanok@emcraft.com
Subject: Re[2]: [PATCH 07/11] md: rewrite handle_stripe_dirtying6 in asynchronous  way
Date: Fri, 16 Jan 2009 17:46:03 +0300	[thread overview]
Message-ID: <1675190812.20090116174603@emcraft.com> (raw)
In-Reply-To: <91b13c310901151707x48b1ef8av1609c3a622c19565@mail.gmail.com>


Hello Cheng,

On Friday, January 16, 2009 you wrote:

> Ack, could you please make the changelog more descriptive?
> and or add some of your benchmark results?

 Of course. We did benchmarking using the Xdd tool like follows:

# xdd -op write -kbytes $kbytes -reqsize $reqsize -dio-passes 2 –verbose -target $target_device

 where

$kbytes = data disks * size of disk
$reqsize= data disks * chunk size
$target_device = /dev/md0

 This way we did write of full array size, and thus achieved the 
maximum performance.

 The test cases were RAID-6 built on the top of 14 S-ATA drives 
connected to 2 LSI cards (7+7) inserted into the 800 MHz Katmai board 
(based on ppc440spe) equipped with 4GB of 800 MHz DRAM .

 Here are the results (Psw - write throughput with s/w RAID-6; Phw - 
write throughput with the h/w accelerated RAID-6):

 PAGE_SIZE=4KB, chunk=64/128/256 KB
        Psw = 71/72/74 MBps
        Phw = 128/136/139 MBps

 PAGE_SIZE=16KB, chunk=256/512/1024 KB
        Psw = 81/81/82 MBps
        Phw = 205/244/239 MBps

 PAGE_SIZE=64KB, chunk=1024/2048/4096 KB
        Psw = 84/84/85 MBps
        Phw = 258/253/258 MBps

 PAGE_SIZE=256KB, chunk=4096/8192/16384 KB
        Psw = 81/83/83 MBps
        Phw = 288/275/274 MBps

 Regards, Yuri

 --
 Yuri Tikhonov, Senior Software Engineer
 Emcraft Systems, www.emcraft.com

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Yuri Tikhonov <yur@emcraft.com>
To: Cheng Renquan <crquan@gmail.com>
Cc: wd@denx.de, dzu@denx.de, linux-raid@vger.kernel.org,
	linuxppc-dev@ozlabs.org, yanok@emcraft.com,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re[2]: [PATCH 07/11] md: rewrite handle_stripe_dirtying6 in asynchronous way
Date: Fri, 16 Jan 2009 17:46:03 +0300	[thread overview]
Message-ID: <1675190812.20090116174603@emcraft.com> (raw)
In-Reply-To: <91b13c310901151707x48b1ef8av1609c3a622c19565@mail.gmail.com>

=0D=0AHello Cheng,

On Friday, January 16, 2009 you wrote:

> Ack, could you please make the changelog more descriptive?
> and or add some of your benchmark results?

 Of course. We did benchmarking using the Xdd tool like follows:

# xdd -op write -kbytes $kbytes -reqsize $reqsize -dio-passes 2 =E2=80=93ve=
rbose -target $target_device

 where

$kbytes =3D data disks * size of disk
$reqsize=3D data disks * chunk size
$target_device =3D /dev/md0

 This way we did write of full array size, and thus achieved the=20
maximum performance.

 The test cases were RAID-6 built on the top of 14 S-ATA drives=20
connected to 2 LSI cards (7+7) inserted into the 800 MHz Katmai board=20
(based on ppc440spe) equipped with 4GB of 800 MHz DRAM .

 Here are the results (Psw - write throughput with s/w RAID-6; Phw -=20
write throughput with the h/w accelerated RAID-6):

 PAGE_SIZE=3D4KB, chunk=3D64/128/256 KB
        Psw =3D 71/72/74 MBps
        Phw =3D 128/136/139 MBps

 PAGE_SIZE=3D16KB, chunk=3D256/512/1024 KB
        Psw =3D 81/81/82 MBps
        Phw =3D 205/244/239 MBps

 PAGE_SIZE=3D64KB, chunk=3D1024/2048/4096 KB
        Psw =3D 84/84/85 MBps
        Phw =3D 258/253/258 MBps

 PAGE_SIZE=3D256KB, chunk=3D4096/8192/16384 KB
        Psw =3D 81/83/83 MBps
        Phw =3D 288/275/274 MBps

 Regards, Yuri

 --
 Yuri Tikhonov, Senior Software Engineer
 Emcraft Systems, www.emcraft.com

  reply	other threads:[~2009-01-16 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 21:57 [PATCH 07/11] md: rewrite handle_stripe_dirtying6 in asynchronous way Yuri Tikhonov
2008-12-08 21:57 ` Yuri Tikhonov
2009-01-15 21:51 ` Dan Williams
2009-01-15 22:21   ` Dan Williams
2009-01-15 22:21     ` Dan Williams
2009-01-16  1:07     ` Cheng Renquan
2009-01-16  1:07       ` Cheng Renquan
2009-01-16 14:46       ` Yuri Tikhonov [this message]
2009-01-16 14:46         ` Re[2]: " Yuri Tikhonov
2009-01-16 14:24     ` Yuri Tikhonov
2009-01-16 14:24       ` Yuri Tikhonov
2009-01-16 18:39       ` Dan Williams
2009-01-16 18:39         ` Dan Williams
2009-01-15 21:51 ` Dan Williams
2009-01-15 21:51 ` Dan Williams

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=1675190812.20090116174603@emcraft.com \
    --to=yur@emcraft.com \
    --cc=crquan@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=dzu@denx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=wd@denx.de \
    --cc=yanok@emcraft.com \
    /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.