From: Tim Moore <linux-raid@nsr500.net>
To: linux-raid@vger.kernel.org
Subject: dd with bytes/sec patch [was: non-optimal RAID 5 performance with 8 drive array]
Date: Wed, 02 Mar 2005 15:08:22 -0800 [thread overview]
Message-ID: <42264766.5070700@nsr500.net> (raw)
In-Reply-To: <6.2.1.2.2.20050301193656.05fb3720@mail.tekno-soft.it>
> 1. Grab coreutils 5.2.1 from gnu.org and the debian patch from
> http://packages.debian.org/unstable/base/coreutils
>
> 2. Extract the 2 dd patches which start with the line
>
> +--- coreutils-5.0/src/dd.c.orig 2003-02-07 07:39:20.000000000 -0500
>
> through, but not including, the line
>
> --- coreutils-5.2.1.orig/debian/patches/19_ipv6
>
> You can see all the patch headers with
> zcat coreutils_5.2.1-2.diff.gz | grep '^---'
>
> 3. Get rid of the extra leading '+' (sed 's/^\+//'). You now have a working dd patch
>
> 4. Apply the patch and compile:
>
> [tim@tim-linux ~/Kits]$ cd coreutils-5.2.1
> [tim@tim-linux coreutils-5.2.1]$ patch -p1 < ../coreutils-5.2.1.dd-performance-counter.patch
> patching file src/dd.c
> Hunk #1 succeeded at 149 (offset -1 lines).
> Hunk #2 succeeded at 377 (offset 11 lines).
> Hunk #3 succeeded at 380 (offset -1 lines).
> Hunk #4 succeeded at 494 (offset 11 lines).
> Hunk #5 succeeded at 1069 (offset -2 lines).
> Hunk #6 succeeded at 1144 (offset 11 lines).
> Hunk #7 succeeded at 1166 with fuzz 2 (offset -2 lines).
> Hunk #8 succeeded at 1268 (offset 12 lines).
> patching file tests/dd/skip-seek
> Hunk #1 succeeded at 20 (offset -1 lines).
> [tim@tim-linux coreutils-5.2.1]$ ./configure -q
> checking how to get filesystem space usage...
> config.status: creating po/POTFILES
> config.status: creating po/Makefile
> [tim@tim-linux coreutils-5.2.1]$ /usr/bin/time make -j2 > /dev/null
> 26.17user 2.23system 0:30.16elapsed 94%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (410381major+274056minor)pagefaults 0swaps
> [tim@tim-linux coreutils-5.2.1]$ ls -l src/dd
> -rwxrwxr-x 1 tim tim 68574 Mar 2 11:18 src/dd
> [tim@tim-linux coreutils-5.2.1]$ su
> Password:
> [tim@tim-linux coreutils-5.2.1]# src/dd if=/dev/hda1 of=/dev/zero bs=4k
> 126504+0 records in
> 126504+0 records out
> 518160384 bytes transferred in 21.705705 seconds (23872083 bytes/sec)
--
next prev parent reply other threads:[~2005-03-02 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 13:24 non-optimal RAID 5 performance with 8 drive array Nicola Fankhauser
2005-03-01 17:53 ` Robin Bowes
2005-03-01 18:04 ` Roberto Fichera
2005-03-01 18:12 ` Robin Bowes
2005-03-01 18:41 ` Roberto Fichera
2005-03-02 23:08 ` Tim Moore [this message]
2005-03-04 22:23 ` Matthias Julius
2005-03-06 14:25 ` Stephan van Hienen
2005-03-06 14:43 ` Nicola Fankhauser
2005-03-06 17:09 ` Stephan van Hienen
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=42264766.5070700@nsr500.net \
--to=linux-raid@nsr500.net \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).