From: Patrick McHardy <kaber@trash.net>
To: Roland Dreier <rdreier@cisco.com>
Cc: Amar Mudrankit <amar.mudrankit@qlogic.com>,
Dave Dillow <dillowda@ornl.gov>, Greg KH <greg@kroah.com>,
general@lists.openfabrics.org, netdev@vger.kernel.org,
Stephen Hemminger <shemminger@vyatta.com>,
poornima.kamath@qlogic.com
Subject: Re: [ofa-general] Re: [PATCH v3 08/13] QLogic VNIC: sysfs interface implementation for the driver
Date: Fri, 06 Jun 2008 00:54:49 +0200 [thread overview]
Message-ID: <48486EB9.4010706@trash.net> (raw)
In-Reply-To: <adave0nzk0k.fsf@cisco.com>
Roland Dreier wrote:
> > > There is nothing stopping adding a well designed alternate interface.
> > > Either netlink or ioctl's are okay. As long as it is 32/64 bit clean.
>
> > From a quick look it seems it should use rtnl_link instead
> > of adding yet another private sysfs interface.
>
> This seems crazy -- why do we want to push things towards the complexity
> of rtnl_link instead of a simple text-based interface that can be
> trivial used with 'echo' from the shell?
Its not complicated at all. Ability to use "echo" seems like a
pretty poor argument to me.
> What advantages does that give?
- atomic configuration changes
- atomic configuration dumps
- configuration change notifications
- same interface as for all other network-related configurations
- easily extensible
- not yet another private driver interface
- not text based, which makes it a lot more convenient for using in programs
next prev parent reply other threads:[~2008-06-05 22:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 9:53 [PATCH v3 00/13] QLogic VNIC Driver Ramachandra K
2008-05-29 9:54 ` [ofa-general] [PATCH v3 01/13] QLogic VNIC: Driver - netdev implementation Ramachandra K
2008-05-29 17:27 ` [ofa-general] " Stephen Hemminger
2008-06-03 12:14 ` Ramachandra K
2008-06-03 17:51 ` Stephen Hemminger
2008-05-29 9:54 ` [ofa-general] [PATCH v3 02/13] QLogic VNIC: Netpath - abstraction of connection to EVIC/VEx Ramachandra K
2008-05-29 9:55 ` [ofa-general] [PATCH v3 03/13] QLogic VNIC: Implementation of communication protocol with EVIC/VEx Ramachandra K
2008-05-29 9:55 ` [ofa-general] [PATCH v3 04/13] QLogic VNIC: Implementation of Control path of communication protocol Ramachandra K
2008-05-29 9:56 ` [ofa-general] [PATCH v3 05/13] QLogic VNIC: Implementation of Data " Ramachandra K
2008-05-29 9:56 ` [ofa-general] [PATCH v3 06/13] QLogic VNIC: IB core stack interaction Ramachandra K
2008-05-29 9:57 ` [ofa-general] [PATCH v3 07/13] QLogic VNIC: Handling configurable parameters of the driver Ramachandra K
2008-05-29 9:57 ` [ofa-general] [PATCH v3 08/13] QLogic VNIC: sysfs interface implementation for " Ramachandra K
2008-05-29 17:30 ` [ofa-general] " Stephen Hemminger
2008-05-29 17:48 ` Greg KH
2008-06-01 5:46 ` Roland Dreier
2008-06-03 12:24 ` [ofa-general] " Ramachandra K
2008-06-03 15:10 ` Roland Dreier
2008-06-03 18:25 ` Amar Mudrankit
2008-06-03 18:30 ` Greg KH
2008-06-03 18:45 ` David Dillow
2008-06-05 4:10 ` Roland Dreier
2008-06-05 5:40 ` Dave Dillow
2008-06-05 16:38 ` Roland Dreier
2008-06-05 17:01 ` Stephen Hemminger
2008-06-05 17:32 ` Patrick McHardy
2008-06-05 20:47 ` Roland Dreier
2008-06-05 22:54 ` Patrick McHardy [this message]
2008-06-05 17:54 ` David Dillow
2008-05-29 9:58 ` [ofa-general] [PATCH v3 09/13] QLogic VNIC: IB Multicast for Ethernet broadcast/multicast Ramachandra K
2008-05-29 9:58 ` [ofa-general] [PATCH v3 10/13] QLogic VNIC: Driver Statistics collection Ramachandra K
2008-05-29 9:59 ` [PATCH v3 11/13] QLogic VNIC: Driver utility file - implements various utility macros Ramachandra K
2008-05-29 9:59 ` [ofa-general] [PATCH v3 12/13] QLogic VNIC: Driver Kconfig and Makefile Ramachandra K
2008-05-29 10:00 ` [ofa-general] [PATCH v3 13/13] QLogic VNIC: Modifications to IB " Ramachandra K
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=48486EB9.4010706@trash.net \
--to=kaber@trash.net \
--cc=amar.mudrankit@qlogic.com \
--cc=dillowda@ornl.gov \
--cc=general@lists.openfabrics.org \
--cc=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=poornima.kamath@qlogic.com \
--cc=rdreier@cisco.com \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.