From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: sysfs question Date: Thu, 12 Nov 2009 09:00:41 -0800 Message-ID: <20091112090041.1536ccc8@nehalam> References: <200911021533.25345.matthias.fuchs@esd.eu> <20091106100427.GB323@e-circ.dyndns.org> <20091109112331.GE323@e-circ.dyndns.org> <4AF83EB7.3070401@grandegger.com> <20091112100053.GA322@e-circ.dyndns.org> <4AFBE0DD.1000408@grandegger.com> <20091112103940.GC322@e-circ.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Wolfgang Grandegger , netdev@vger.kernel.org To: Kurt Van Dijck Return-path: Received: from mail.vyatta.com ([76.74.103.46]:33162 "EHLO mail.vyatta.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753402AbZKLRBF (ORCPT ); Thu, 12 Nov 2009 12:01:05 -0500 In-Reply-To: <20091112103940.GC322@e-circ.dyndns.org> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 12 Nov 2009 11:39:41 +0100 Kurt Van Dijck wrote: > Hi, > > Within the socketcan project, we came into a situation that > might benefit with input from the netdev mailing list. > > The main issue is the policy to add sysfs properties in > /sys/class/net/canX. > > The reason for this is that cards (devices) with multiple network > interfaces may require properties per network. > > An obvious property would be the 'channel number of the card'. Other > properties could be things like type of output circuitry, ..., rather > hardware specific. > > I see currently 3 options: > 1) such properties in /sys/class/net/canX would be allowed. > 2) such properties would belong in /sys/class/net/canX// > 3) such properties would go somewhere else. > > Some input with regard to sysfs policies would be helpfull. > > Kurt It sounds like the property you are proposing is a property of the upper network layer not the hardware. Putting more properties in sysfs is good if is hardware related, but awkward if it is really a protocol attribute.