linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Joel Becker <Joel.Becker@oracle.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-fsdevel@vger.kernel.org,
	Wim Coekaerts <wim.coekaerts@oracle.com>
Subject: Re: [Joel.Becker@oracle.com: Re: [Linux-cluster] Re: [PATCH 1/3] dlm: use configfs]
Date: Thu, 25 Aug 2005 10:45:42 -0700	[thread overview]
Message-ID: <20050825174541.GA21228@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20050825095819.GA4785@lst.de>

On Thu, Aug 25, 2005 at 11:58:19AM +0200, Christoph Hellwig wrote:
> > 	The vma-walking will go away, replaced by another mmap scheme
> > entirely.  However, that's three or four months away.  The current code
> > is merely a stopgap for now. 
> > 	Many folks have an interest in having a cluster filesystem in
> > mainline.  This seems like an issue that can be resolved later, not a
> > big blocker.  That is, it would be worth more to people to have it in
> > mainline for the next four months, knowing this will get fixed, than
> > keeping it out of mainline for four months over this feature.
> 
> I don't think it'll take four month, but we're having a bad predence
> here - GFS pretty much duplicates the same mess and if we let that
> in we're growing more and more of it.  Please get it right conceptually
> first, it doesn't have to be perfect.

We're fixing this by taking a completely different approach from what is
done today, which won't involve vma walking. It *will* take some time
however, at least in testing and validation. In the meantime I'd rather not
see us do all the work to port something to the VFS which we won't even be
using in a few months time.

> > >  - there's still some procfs abuse
> > 
> > 	Specifics of what is abuse vs OK would be interesting.
> 
> You're using procfs for non-process data.

I'm not sure I understand this... Looking through /proc I see lots of
subsystems using /proc in similar ways to us. or is there a very specific
method which you have a problem with?
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com


  reply	other threads:[~2005-08-25 17:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050822213220.GH19387@insight.us.oracle.com>
     [not found] ` <20050822144521.24494329.akpm@osdl.org>
     [not found]   ` <20050822215049.GI19387@insight.us.oracle.com>
     [not found]     ` <20050822150505.7978136d.akpm@osdl.org>
2005-08-24  7:18       ` [Joel.Becker@oracle.com: Re: [Linux-cluster] Re: [PATCH 1/3] dlm: use configfs] Christoph Hellwig
2005-08-24 20:33         ` Joel Becker
2005-08-25  9:58           ` Christoph Hellwig
2005-08-25 17:45             ` Mark Fasheh [this message]
2005-08-28 22:48               ` Greg KH
2005-08-29 17:41                 ` Joel Becker
2005-08-29 19:29                   ` Miklos Szeredi
2005-08-31  6:14                     ` Greg KH
2005-08-31  8:24                       ` Joel Becker
2005-08-31 11:11                       ` Miklos Szeredi
2005-08-25 18:45             ` Zach Brown
2005-08-25 20:23               ` Christoph Hellwig

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=20050825174541.GA21228@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=Joel.Becker@oracle.com \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=wim.coekaerts@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).