From: Joel Becker <Joel.Becker@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux kernel <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Satyam Sharma <ssatyam@cse.iitk.ac.in>,
Felix Fietkau <nbd@openwrt.org>, Al Viro <viro@ftp.linux.org.uk>,
"H. Peter Anvin" <hpa@kernel.org>
Subject: Re: Is configfs the right solution for configuration based fs?
Date: Sun, 8 Jun 2008 19:28:21 -0700 [thread overview]
Message-ID: <20080609022821.GL29740@mail.oracle.com> (raw)
In-Reply-To: <43e72e890806081425h4e785800nc618fc1985f9809f@mail.gmail.com>
On Sun, Jun 08, 2008 at 02:25:36PM -0700, Luis R. Rodriguez wrote:
> I was really interested in looking to start a filesystem based
> approach for configuration of wireless a while back, an alternative to
> nl80211 if you will, but I stopped after I was told about some major
> issues with configfs. I forget the issues raised clearly so I'd like
> to bring this up for debate to see what really are the issues, what
> needs to be fixed so we can *properly* use a fs for configuration of
> subsystems. I thought configfs was the solution. We currently use and
> abuse debugfs, but it doesn't matter -- we don't expect users to
> depend on those files for ABI. It, however, it would be nice to
> finally export some of these values into a concise place so userspace
> *can* rely on them.
I'd love to hear about the issues as well. I'd also love to see
what you require, so as to either be able to explain how configfs can do
it for you, or to say that configfs isn't the right fit. configfs is
designed with a particular goal, and some things don't fit that - and
that's fine.
> Perhaps a fs is not even the most optimized approach for size anyway
> so the benefits may just be helping with the easy design of userspace
> applications. Feedback on experiences are welcomed.
>
> PS. I'm hoping those who *really* hate configs can comment
You probably expect me to be all "configfs solves world peace,
how can you hate it?" Nah. I'd really like to understand your need and
how configfs doesn't fit. configfs may not fit. configfs may fit and
I need to explain it better. Or configfs may not fit but should, and we
then can see how to make it right.
Joel
--
"Nothing is wrong with California that a rise in the ocean level
wouldn't cure."
- Ross MacDonald
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2008-06-09 2:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 21:25 Is configfs the right solution for configuration based fs? Luis R. Rodriguez
2008-06-09 2:28 ` Joel Becker [this message]
2008-06-11 9:04 ` Joel Becker
2008-06-09 9:03 ` Johannes Berg
2008-06-10 0:12 ` Ben Nizette
2008-06-10 8:01 ` Johannes Berg
2008-06-10 8:12 ` Luis R. Rodriguez
2008-06-10 22:12 ` Ben Nizette
2008-06-19 2:48 ` [RFC PATCHES] " Joel Becker
2008-06-20 6:19 ` Ben Nizette
2008-06-20 6:52 ` Joel Becker
2008-06-20 9:22 ` Ben Nizette
2008-06-20 21:37 ` Joel Becker
2008-06-21 1:03 ` Ben Nizette
2008-06-21 2:02 ` Joel Becker
2008-06-21 8:03 ` Ben Nizette
2008-06-21 8:44 ` Joel Becker
2008-06-21 11:44 ` Ben Nizette
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=20080609022821.GL29740@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=greg@kroah.com \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=nbd@openwrt.org \
--cc=ssatyam@cse.iitk.ac.in \
--cc=viro@ftp.linux.org.uk \
/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).