mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Nizette <bn@niasdigital.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linux kernel <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Joel Becker <joel.becker@oracle.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: Tue, 10 Jun 2008 10:01:20 +0200	[thread overview]
Message-ID: <1213084880.22220.29.camel@johannes.berg> (raw)
In-Reply-To: <1213056772.4089.42.camel@moss.renham>

[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]

On Tue, 2008-06-10 at 10:12 +1000, Ben Nizette wrote:
> On Mon, 2008-06-09 at 11:03 +0200, Johannes Berg wrote:
> 
> > Personally, I have a few issues with this:
> >  1) why bother with a second configuration interface that we have to
> >     maintain, adjust, ...? if we need scriptable access, then make a
> >     good userspace tool that is scriptable.
> 
> What's the first one, sysfs..?  ioctl (eww..)?  

netlink.

> >  2) string-based stuff is often messy, especially the varying attributes
> >     like MAC addresses etc. Unless we just use binary files again, which
> >     is not very useful again. Take, for example, the monitor flags. If
> >     we use the same flags then nobody really knows what's up 
> >     (echo 0x3 > mntr_flags?) and if we use strings then we cannot easily
> >     ever rename the flag while keeping ABI/API compatibility.
> 
> Not sure I see the argument here, why would you want to change the flag
> name?  If you decide the old name is stupid then can't you just alias
> the old name to the new one?

Sure can do, but it just adds a lot of complexity to the kernel. I don't
see the point, it's not like you need a lot of code to build netlink
messages. Heck, I've done it by _hand_ and used just netlink sockets.
It's not a lot of code.

> String handling is always a bit iffy, though it has to be done
> somewhere, either in kernel or in your "good userspace tool which is
> scriptable".  I'd prefer to have it done once, well, in the kernel and
> not have to ship more software than necessary.

I personally prefer to put it into userspace.

> >  3) afaik configfs doesn't actually support the mkdir, ... stuff yet
> >     that you want for virtual interfaces.
> 
> It has all the  mkdir stuff I can think of, can you elaborate?  It
> doesn't have the commitable object support but I just have an 'enabled'
> attribute in there to switch the thing on and off.

I don't remember the specifics, it's been a while, I guess I could be
thinking of the commitable object support; mostly we'd want to configure
many things in one go, even on a live object. Without disabling that
object first, obviously.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2008-06-10  8:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08 21:25 Luis R. Rodriguez
2008-06-09  2:28 ` Joel Becker
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 [this message]
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=1213084880.22220.29.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=bn@niasdigital.com \
    --cc=greg@kroah.com \
    --cc=hpa@kernel.org \
    --cc=joel.becker@oracle.com \
    --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

all inboxes | Powered by JetHome®