From: David Chinner <dgc@sgi.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: Rik van Riel <riel@redhat.com>, Nick Piggin <npiggin@suse.de>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Hugh Dickins <hugh@veritas.com>,
Jared Hulbert <jaredeh@gmail.com>,
Chris Mason <chris.mason@oracle.com>, David Chinner <dgc@sgi.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Neil Brown <neilb@suse.de>, Joern Engel <joern@logfs.org>,
Miklos Szeredi <miklos@szeredi.hu>, Mingming Cao <cmm@us.ibm.com>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: vm/fs meetup details
Date: Fri, 6 Jul 2007 07:27:57 +1000 [thread overview]
Message-ID: <20070705212757.GB12413810@sgi.com> (raw)
In-Reply-To: <137D15F6-EABE-4EC1-A3AF-DAB0A22CF4E3@oracle.com>
On Thu, Jul 05, 2007 at 01:40:08PM -0700, Zach Brown wrote:
> >- repair driven design, we know what it is (Val told us), but
> > how does it apply to the things we are currently working on?
> > should we do more of it?
>
> I'm sure Chris and I could talk about the design elements in btrfs
> that should aid repair if folks are interested in hearing about
> them. We'd keep the hand-waving to a minimum :).
And I'm sure I could provide a counterpoint by talking about
the techniques we've used improving XFS repair speed and
scalability without needing to change any on disk formats....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
WARNING: multiple messages have this Message-ID (diff)
From: David Chinner <dgc@sgi.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: Rik van Riel <riel@redhat.com>, Nick Piggin <npiggin@suse.de>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Hugh Dickins <hugh@veritas.com>,
Jared Hulbert <jaredeh@gmail.com>,
Chris Mason <chris.mason@oracle.com>, David Chinner <dgc@sgi.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Neil Brown <neilb@suse.de>, Joern Engel <joern@logfs.org>,
Miklos Szeredi <miklos@szeredi.hu>, Mingming Cao <cmm@us.ibm.com>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: vm/fs meetup details
Date: Fri, 6 Jul 2007 07:27:57 +1000 [thread overview]
Message-ID: <20070705212757.GB12413810@sgi.com> (raw)
In-Reply-To: <137D15F6-EABE-4EC1-A3AF-DAB0A22CF4E3@oracle.com>
On Thu, Jul 05, 2007 at 01:40:08PM -0700, Zach Brown wrote:
> >- repair driven design, we know what it is (Val told us), but
> > how does it apply to the things we are currently working on?
> > should we do more of it?
>
> I'm sure Chris and I could talk about the design elements in btrfs
> that should aid repair if folks are interested in hearing about
> them. We'd keep the hand-waving to a minimum :).
And I'm sure I could provide a counterpoint by talking about
the techniques we've used improving XFS repair speed and
scalability without needing to change any on disk formats....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-05 21:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 4:01 vm/fs meetup details Nick Piggin
2007-07-05 4:01 ` Nick Piggin
2007-07-05 14:32 ` Peter Zijlstra
2007-07-05 14:32 ` Peter Zijlstra
2007-07-05 17:54 ` Rik van Riel
2007-07-05 17:54 ` Rik van Riel
2007-07-05 20:40 ` Zach Brown
2007-07-05 20:40 ` Zach Brown
2007-07-05 21:27 ` David Chinner [this message]
2007-07-05 21:27 ` David Chinner
2007-07-05 21:40 ` Rik van Riel
2007-07-05 21:40 ` Rik van Riel
2007-07-06 2:26 ` Nick Piggin
2007-07-06 2:26 ` Nick Piggin
2007-07-06 10:01 ` David Chinner
2007-07-06 10:01 ` David Chinner
2007-07-06 10:26 ` Jörn Engel
2007-07-06 10:26 ` Jörn Engel
2007-07-06 13:42 ` David Chinner
2007-07-06 13:42 ` David Chinner
2007-07-06 13:52 ` Chris Mason
2007-07-06 13:52 ` Chris Mason
2007-07-06 15:57 ` Jörn Engel
2007-07-06 15:57 ` Jörn Engel
2007-07-06 15:58 ` Steven Whitehouse
2007-07-06 15:58 ` Steven Whitehouse
2007-07-06 23:47 ` Neil Brown
2007-07-06 23:47 ` Neil Brown
2007-07-06 2:00 ` Nick Piggin
2007-07-06 2:00 ` Nick Piggin
2007-07-06 20:40 ` Christoph Lameter
2007-07-06 20:40 ` Christoph Lameter
2007-07-07 10:45 ` Jörn Engel
2007-07-07 10:45 ` Jörn Engel
2007-07-08 23:29 ` David Chinner
2007-07-08 23:29 ` David Chinner
2007-07-09 0:27 ` Jörn Engel
2007-07-09 0:27 ` Jörn Engel
2007-07-09 15:53 ` Martin Bligh
2007-07-09 15:53 ` Martin Bligh
2007-07-27 14:30 ` Dave Kleikamp
2007-07-27 14:30 ` Dave Kleikamp
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=20070705212757.GB12413810@sgi.com \
--to=dgc@sgi.com \
--cc=aia21@cam.ac.uk \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=jaredeh@gmail.com \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
--cc=npiggin@suse.de \
--cc=riel@redhat.com \
--cc=suparna@in.ibm.com \
--cc=trond.myklebust@fys.uio.no \
--cc=zach.brown@oracle.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.