netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Timo Teräs" <ext-timo.teras@nokia.com>
To: ext ext Christoph Hellwig <hch@infradead.org>
Cc: davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH] Add ability to register class interfaces for network class
Date: Wed, 27 Oct 2004 14:31:04 +0300	[thread overview]
Message-ID: <417F86F8.6020004@nokia.com> (raw)
In-Reply-To: <20041027111317.GA27240@infradead.org>

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

ext ext Christoph Hellwig wrote:
>>I pointed out the reason why I need it: to add an attribute:
>>/sys/class/net/<interface>/<new_attribute>. Others might want to do this
>>too.
>>
>>Also the interface subsystem is used in many places (eg. i2o) to create
>>all the sysfs entries. Maybe it'd be useful to do in net class as well.
>>And if'd make separate interfaces for standard attributes and wireless
>>attributes. That way you'd get rid of the #ifdefs of WIRELESS_EXT in
>>net-sysfs.c.
>>
>>On the other hand you didn't answer my question: why the
>>interface registration should not be possible?
>>Documentation/driver-model/interface.txt states that this is exactly the
>>thing it should be used for.
> 
> Because we don't add interfaces for the sake of it. You still haven't show
> the user that wants this.  i you presented a sane user the review would be
> quite different.

I am the user wanting it :)

If you want to look more detailed what I'm trying to accomplish you could check:
http://seclists.org/lists/linux-kernel/2004/Oct/1373.html
http://seclists.org/lists/linux-kernel/2004/Sep/8685.html
http://lists.netfilter.org/pipermail/netfilter-devel/2004-August/016342.html

Of course the ideal way to do this would be adding a timer to net_device and 
modifying net-sysfs.c. But I don't think that is going to happen so I want to 
do as unintrusive implementation as possible. And currently I think it'd be 
adding an interface to network class device which creates the related attribute.

Cheers,
   Timo

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-10-27 11:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 18:35 [PATCH] Add ability to register class interfaces for network class Timo Teräs
2004-10-26 18:48 ` Christoph Hellwig
2004-10-26 20:52   ` Teras Timo (EXT-YomiGroup/Helsinki)
2004-10-27 11:13     ` ext Christoph Hellwig
2004-10-27 11:31       ` Timo Teräs [this message]
2004-10-27 15:59         ` Stephen Hemminger
2004-10-27 18:38           ` Teras Timo (EXT-YomiGroup/Helsinki)
2004-10-27 18:55             ` Stephen Hemminger
2004-10-27 19:20               ` Teras Timo (EXT-YomiGroup/Helsinki)

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=417F86F8.6020004@nokia.com \
    --to=ext-timo.teras@nokia.com \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=netdev@oss.sgi.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).