From: "David S. Miller" <davem@davemloft.net>
To: Ben Greear <greearb@candelatech.com>
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: RFC: Redirect-Device
Date: Thu, 31 Mar 2005 14:33:42 -0800 [thread overview]
Message-ID: <20050331143342.594b70d9.davem@davemloft.net> (raw)
In-Reply-To: <424C7929.6080200@candelatech.com>
On Thu, 31 Mar 2005 14:26:49 -0800
Ben Greear <greearb@candelatech.com> wrote:
> Stephen Hemminger wrote:
>
> > Other possiblity is adding additional attributes onto the device with sysfs.
> > That is what net/bridge/br_sysfs_if.c does. I'm not claiming it is a pretty
> > kernel programming model, but the user side API is simpler.
>
> I prefer to stay away from sysfs. procfs may have it's faults, but at
> least in this case, it is quite straight-forward and easily does what
> I need. And procfs is less encumbered by flame wars :)
Are you shying away from sysfs merely for encumberance reasons?
You've dissed Jamal's excellent TC action infrastructure, you're
now dissing sysfs as well which can also solve your problems.
All new interfaces are being done through sysfs, that's simply a
fact of life in the kernel. If you want to buck this trend, you
have to come up with a much better argument than "procfs is more
straight-forward". Well if sysfs isn't as straightforward, suggest
a layer of interfaces that might make it so.
next prev parent reply other threads:[~2005-03-31 22:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 20:41 RFC: Redirect-Device Ben Greear
2005-03-31 21:02 ` David S. Miller
2005-03-31 21:05 ` Stephen Hemminger
2005-03-31 21:45 ` Ben Greear
2005-03-31 21:52 ` David S. Miller
2005-03-31 22:04 ` Ben Greear
2005-03-31 22:21 ` David S. Miller
2005-03-31 22:05 ` Stephen Hemminger
2005-03-31 22:26 ` Ben Greear
2005-03-31 22:33 ` David S. Miller [this message]
2005-03-31 22:42 ` Ben Greear
2005-03-31 22:43 ` David S. Miller
2005-03-31 21:13 ` jamal
2005-03-31 21:26 ` Ben Greear
2005-03-31 21:53 ` jamal
2005-03-31 22:22 ` Ben Greear
2005-03-31 22:35 ` David S. Miller
2005-03-31 22:54 ` Ben Greear
2005-03-31 23:26 ` jamal
2005-03-31 23:56 ` Ben Greear
2005-04-01 0:53 ` jamal
2005-04-01 9:01 ` bert hubert
2005-04-01 16:58 ` Ben Greear
2005-03-31 22:46 ` Thomas Graf
2005-03-31 23:00 ` Ben Greear
2005-03-31 23:20 ` jamal
2005-03-31 23:35 ` Ben Greear
2005-03-31 23:46 ` jamal
2005-04-02 8:41 ` Meelis Roos
2005-04-02 21:08 ` jamal
2005-04-01 5:03 ` Pekka Savola
2005-04-01 5:27 ` Ben Greear
2005-04-01 9:28 ` Pekka Savola
2005-04-01 16:29 ` Ben Greear
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=20050331143342.594b70d9.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/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).