From: sqweek <sqweek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sd(3) and concurrent readers/writers?
Date: Tue, 15 Sep 2009 02:43:37 +0800 [thread overview]
Message-ID: <140e7ec30909141143t5c700ed3ka9ad3437ce9dfee1@mail.gmail.com> (raw)
In-Reply-To: <4672ddba9b22be0ab00effce6cae068f@quanstro.net>
2009/9/13 erik quanstrom <quanstro@quanstro.net>:
> but i was
> wondering why cmp would just work. it occurred to me that
> i could run the dds in parallel with a command like this
> cmp <{dd -if data -bs 64k -count 20000} <{dd -if ../sda1/data -bs 64k -count 20000}
Cmp was actually my original method, it wasn't until things started
going funny that I switched to md5sum, to rule out <{} as a potential
problem source and get some more feedback on the blocks themselves.
> surprisingly, this was just as fast on my setup as the specalized
> program
That is interesting to hear though :)
-sqweek
PS. not much progress on my server - having trouble getting ethernet
up to connect to sources and check out your sd stuff.
prev parent reply other threads:[~2009-09-14 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 18:08 sqweek
2009-09-12 18:23 ` erik quanstrom
2009-09-13 14:44 ` erik quanstrom
2009-09-14 18:43 ` sqweek [this message]
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=140e7ec30909141143t5c700ed3ka9ad3437ce9dfee1@mail.gmail.com \
--to=sqweek@gmail.com \
--cc=9fans@9fans.net \
/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).