mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: Paul Menage <menage@google.com>, Greg KH <gregkh@suse.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unlimited read buffer support on configfs
Date: Wed, 11 Oct 2006 23:54:17 -0700	[thread overview]
Message-ID: <20061012065417.GN7911@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1160615452.6389.91.camel@linuxchandra>

On Wed, Oct 11, 2006 at 06:10:52PM -0700, Chandra Seetharaman wrote:
> So, what you are saying is that we should not be using configfs, even
> though it fits nicely except the fact that we are not fitting the "one
> file == one attribute" model ?
> 
> In other words, write our own file system instead of expanding the
> existing infrastructure (just to have one additional feature) ?

	No, I'm not saying that you shouldn't use configfs.  Greg is
more adamant than I, actually, on the "file == attribute" model.
	Here's the thing.  For most users, there is no reason they can't
use configfs for _config_ and something like netlink for bulk data
movement.  configfs isn't a kitchen sink, and it never should be.
	Now, I know that your group/pids list fits really nicely as a
concept in the configfs tree.  You certainly can't be calling a usermode
helper for each fork() and exit().  So this is why we're still having a
discussion and working on it.

> I think we should be talking these in lkml as it is more on the
> philosophical discusiion than a technical discussion. 

	Fair enough, Cc'd!

Joel

-- 

"The question of whether computers can think is just like the question
 of whether submarines can swim."
	- Edsger W. Dijkstra

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

           reply	other threads:[~2006-10-12  6:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1160615452.6389.91.camel@linuxchandra>]

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=20061012065417.GN7911@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=sekharan@us.ibm.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

all inboxes | Powered by JetHome®