public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Kendall <wkendall@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/8] xfsdump: enable support for multiple streams
Date: Thu, 03 Nov 2011 07:11:42 -0500	[thread overview]
Message-ID: <4EB284FE.2040409@sgi.com> (raw)
In-Reply-To: <20111103101908.GA8572@infradead.org>

On 11/03/2011 05:19 AM, Christoph Hellwig wrote:
> On Wed, Nov 02, 2011 at 04:10:46PM -0500, Bill Kendall wrote:
>> This series resurrects the IRIX multi-stream support for splitting a
>> backup among several output files/tapes. This offers some nice
>> performance improvements, particularly in xfsrestore where a single
>> stream often cannot keep the filesystem/disks busy. I've observed
>> a 1.7x improvement on a backup and a 5x improvement on restore.
>>
>> I have a couple of xfstests for this, and will submit those once
>> a few outstanding xfsdump test patches have been reviewed.
>
> I've put both your two previous xfsdump patches and the all your
> xfstests changes into the kernel.org repositories.  They all look
> fine to me.

Thanks for the reviews. I'm going to be out of town for a few days
but will look at your suggestion to use POSIX semaphores when I
return.

>
> Btw, one thing I'd love to see is a script that uses the userspace
> iscsi target (tgt) infrastructure to emulate a tape, and thus allow to
> run the tape tests in any VM without requiring a real tape device.
>
> Maybe there is someone on the list feels challenged by this?

I've been using an open source vtl to achieve the same goal, and have
given some thought to integrating (or at a minimum documenting) how
to use it with the xfsdump tests.

https://github.com/markh794/mhvtl

Bill

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2011-11-03 12:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 21:10 [PATCH 0/8] xfsdump: enable support for multiple streams Bill Kendall
2011-11-02 21:10 ` [PATCH 1/8] xfsdump: link with libpthread Bill Kendall
2011-11-03  8:21   ` Christoph Hellwig
2011-11-02 21:10 ` [PATCH 2/8] xfsdump: remove multi-stream synchronous dir dump Bill Kendall
2011-11-03  8:22   ` Christoph Hellwig
2011-11-02 21:10 ` [PATCH 3/8] xfsdump: implement lock abstraction with pthreads Bill Kendall
2011-11-03  7:10   ` Christoph Hellwig
2011-11-02 21:10 ` [PATCH 4/8] xfsdump: simplify qlock ordinal bitmap Bill Kendall
2011-11-03  8:30   ` Christoph Hellwig
2011-11-02 21:10 ` [PATCH 5/8] xfsdump: convert IRIX sproc threads to pthreads Bill Kendall
2011-11-03  8:31   ` Christoph Hellwig
2011-11-02 21:10 ` [PATCH 6/8] xfsdump: process thread exit status Bill Kendall
2011-11-03  8:32   ` Christoph Hellwig
2011-11-02 21:10 ` [PATCH 7/8] xfsdump: path lookup cache must be thread specific Bill Kendall
2011-11-03  8:33   ` Christoph Hellwig
2011-11-02 21:10 ` [PATCH 8/8] xfsdump: enable multiple streams Bill Kendall
2011-11-03  8:36   ` Christoph Hellwig
2011-11-03 10:19 ` [PATCH 0/8] xfsdump: enable support for " Christoph Hellwig
2011-11-03 12:11   ` Bill Kendall [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=4EB284FE.2040409@sgi.com \
    --to=wkendall@sgi.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox