linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: David Chinner <dgc@sgi.com>, Zach Brown <zach.brown@oracle.com>,
	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>,
	"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,
	Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
	Steven Whitehouse <steve@chygwyn.com>,
	Dave McCracken <dave.mccracken@oracle.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: vm/fs meetup details
Date: Fri, 6 Jul 2007 04:26:51 +0200	[thread overview]
Message-ID: <20070706022651.GG14215@wotan.suse.de> (raw)
In-Reply-To: <468D6569.6050606@redhat.com>

On Thu, Jul 05, 2007 at 05:40:57PM -0400, Rik van Riel wrote:
> David Chinner wrote:
> >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....
> 
> Sounds like that could be an interesting discussion.
> 
> Especially when trying to answer questions like:
> 
> "At what filesystem size will the mitigating fixes no
>  longer be enough?"
> 
> and
> 
> "When will people start using filesystems THAT big?"  :)

Keep in mind that the way to get the most out of this meeting
is for the fs people to have topics of the form "we'd really
like to do X, can we get some help from the VM"? Or vice versa
from vm people.

That said, we can talk about whatever interests the group on
the day. And that could definitely include issues common to
different filesystems.


  reply	other threads:[~2007-07-06  2:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  4:01 vm/fs meetup details Nick Piggin
2007-07-05 14:32 ` Peter Zijlstra
2007-07-05 17:54 ` Rik van Riel
2007-07-05 20:40   ` Zach Brown
2007-07-05 21:27     ` David Chinner
2007-07-05 21:40       ` Rik van Riel
2007-07-06  2:26         ` Nick Piggin [this message]
2007-07-06 10:01           ` David Chinner
2007-07-06 10:26             ` Jörn Engel
2007-07-06 13:42               ` David Chinner
2007-07-06 13:52                 ` Chris Mason
2007-07-06 15:57                   ` Jörn Engel
2007-07-06 15:58                     ` Steven Whitehouse
2007-07-06 23:47                       ` Neil Brown
2007-07-06  2:00   ` Nick Piggin
2007-07-06 20:40     ` Christoph Lameter
2007-07-07 10:45       ` Jörn Engel
2007-07-08 23:29         ` David Chinner
2007-07-09  0:27           ` Jörn Engel
2007-07-09 15:53             ` Martin Bligh
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=20070706022651.GG14215@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=aia21@cam.ac.uk \
    --cc=chris.mason@oracle.com \
    --cc=cmm@us.ibm.com \
    --cc=dave.mccracken@oracle.com \
    --cc=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=hugh@veritas.com \
    --cc=jaredeh@gmail.com \
    --cc=joern@logfs.org \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@mbligh.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@suse.de \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=steve@chygwyn.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 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).