All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Migrating LVM
Date: Wed, 21 Apr 2010 12:00:46 -0500	[thread overview]
Message-ID: <1271869246.10836.0@raydesk1.bettercgi.com> (raw)
In-Reply-To: <4BCF276A.1040907@cfl.rr.com> (from psusi@cfl.rr.com on Wed Apr 21 11:27:22 2010)

> Oops, my eyes missed the pipe and second dd when I made my previous
> comments.  That is pretty good for different disks then yes... not
> so good for same physical disk.

    Indeed my tests were done copying from the "old" disk
to the "new" disk, as the OP is doing, I believe.

> I actually have some old hacked up dd code I made once to use 16
> concurrent aio requests with O_DIRECT.  I need to clean it up a
> bit but it showed great promise.

    Considering how often "dd" is used for copying large amounts
of data, even a modest improvement could save many thousands of
hours of admin time.  I would like to encourage you to do any
needed cleanup and make it available, preferably integrated with
GNU dd - it could save hundreds of thousands of dollars worth of
time.
--
Ray Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php


On 04/21/2010 11:27:22 AM, Phillip Susi wrote:
> On 4/21/2010 11:36 AM, malahal@us.ibm.com wrote:
> > Interesting! You are doing direct I/O to avoid copying from cache  
> to user
> > buffer for read and vice-versa for write, but you are losing the  
> ability
> > to do them parallel! You are doing the next best, that is creating  
> two
> > "dd" threads -- one for reading and another for writing. Since the  
> pipe
> > is really implemented in memory, why should this be faster than  
> normal
> > "dd" that uses page cache? Likely that kswapd is not kicking early
> > enough?
> 
> Oops, my eyes missed the pipe and second dd when I made my previous
> comments.  That is pretty good for different disks then yes... not so
> good for same physical disk.
> 
> > Enhancing "dd" to create a reader and a writer thread would really
> > help, I believe.
> 
> I actually have some old hacked up dd code I made once to use 16
> concurrent aio requests with O_DIRECT.  I need to clean it up a bit  
> but
> it showed great promise.
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 
> 

  reply	other threads:[~2010-04-21 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  4:06 [linux-lvm] Migrating LVM M.Lewis
2010-04-21  5:42 ` Luca Berra
2010-04-21 14:18 ` Ray Morris
2010-04-21 15:36   ` malahal
2010-04-21 16:27     ` Phillip Susi
2010-04-21 17:00       ` Ray Morris [this message]
2010-04-21 23:10         ` M.Lewis
2010-04-21 16:24   ` Phillip Susi

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=1271869246.10836.0@raydesk1.bettercgi.com \
    --to=support@bettercgi.com \
    --cc=linux-lvm@redhat.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.