All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zach Brown <zab@zabbo.net>
To: faibish_sorin@emc.com
Cc: sarah.jelinek@intel.com, adilger@whamcloud.com,
	linux-fsdevel@vger.kernel.org
Subject: Re: Inode metadata and file data syncing
Date: Thu, 19 Jul 2012 09:49:05 -0700	[thread overview]
Message-ID: <20120719164905.GC3889@lenny.home.zabbo.net> (raw)
In-Reply-To: <F0897B83F4BC10458936F08DADF233160D547861C3@MX02A.corp.emc.com>

On Thu, Jul 19, 2012 at 09:50:59AM -0400, faibish_sorin@emc.com wrote:
> I am simply curious what all the current file systems features we lack
> today as maybe others can contribute. Hope this makes sense

It doesn't take much effort to imagine features which are tied to
hardware that is still under wraps and which make current designs look
completely silly.  I'm willing to give them the benefit of the doubt.

I'm happy that they're engaging with fsdevel early, even if its clumsy
because they can't really talk about details.  I think it's worth
spending a small amount of time to help them understand the (very
confusing!) fs paths.  It has a decent chance of reducing the number of
problems in the code we'll no doubt see some day and have to review.

- z

  reply	other threads:[~2012-07-19 16:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 16:53 Inode metadata and file data syncing Jelinek, Sarah
2012-07-18 17:21 ` Josef Bacik
2012-07-18 17:52   ` Jelinek, Sarah
2012-07-19  1:48 ` Andreas Dilger
2012-07-19 12:44   ` Jelinek, Sarah
2012-07-19 13:12     ` faibish_sorin
2012-07-19 13:18       ` Jelinek, Sarah
2012-07-19 13:50         ` faibish_sorin
2012-07-19 16:49           ` Zach Brown [this message]
2012-07-19 17:11             ` Andreas Dilger
2012-07-19 18:08               ` Matthew Wilcox

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=20120719164905.GC3889@lenny.home.zabbo.net \
    --to=zab@zabbo.net \
    --cc=adilger@whamcloud.com \
    --cc=faibish_sorin@emc.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sarah.jelinek@intel.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.