lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTikL6u4Kzd1jibp77GMZfMebxusoDX39dPsNK3RW@mail.gmail.com> Date: Wed, 6 Oct 2010 18:06:52 +0200 From: Bart Van Assche <bvanassche@....org> To: Stephen Hemminger <shemminger@...tta.com> Cc: Bernard Metzler <bmt@...ich.ibm.com>, netdev@...r.kernel.org, linux-rdma@...r.kernel.org Subject: Re: [PATCH] SIW: Module initialization On Wed, Oct 6, 2010 at 12:02 AM, Stephen Hemminger <shemminger@...tta.com> wrote: > On Tue, 5 Oct 2010 12:57:21 +0200 > Bart Van Assche <bvanassche@....org> wrote: > >> > + * TODO: Dynamic device management (network device registration/removal). >> >> The current implementation is such that one siw device is created for >> each network device found at kernel module load time. That means that >> you force the user to load the siw kernel module after all other >> kernel modules that register a network device. I'm not sure that's a >> good idea. > > Then device should be controlled by a netlink (rtnl_link_ops) style > interface see vlan_netlink.c. Using netlink is extensible and provides > a cleaner interface than all these other parameterization methods. That will be a lot more work to implement than what Jason proposed: adding a sysfs variable per Ethernet driver, e.g. /sys/class/net/eth0/enable_iwarp. Bart. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists