Date: Sat, 26 Jul 2014 08:24:04 +0100 From: Dominic Froud <dom@talk2dom.com> To: freebsd-net@freebsd.org Subject: Re: Using lagg Message-ID: <53D35794.4030305@talk2dom.com> In-Reply-To: <CAF1ma4wz_1ySJnEM2PS0JCNgum2rhmG%2BJtEi13-h=_vW4Lx4tw@mail.gmail.com> References: <CAF1ma4wm6wpfO-OuSDqxq68K1-coxJyiqVEWD_PeTCnz-FrYyg@mail.gmail.com> <371D9ED786FD4379859A0993E8D12F15@multiplay.co.uk> <CAF1ma4w8QkM_SiEwha_UfZd7n89Lta5bRxyS6c90v=iH7ELY2Q@mail.gmail.com> <20140725222824.GN1065@hub.FreeBSD.org> <CAF1ma4wz_1ySJnEM2PS0JCNgum2rhmG%2BJtEi13-h=_vW4Lx4tw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/07/2014 23:32, Sridhar Iyer wrote: > I was looking at sys/net/if_lagg.c, and wanted to know the usage of > functions such as lagg_ioctl(), lagg_input() etc. > > Regards, > > Sridhar > Those functions are part of the implementation of the lagg driver, internal to the kernel. They generally mirror similarly-named functions for all network drivers. xxx_ioctl() is for processing ioctl() calls from userland xxx_input() is for processing packets that arrive at the interface xxx_start() is for processing packets that are outbound from the interface xxx_create() for creating a new lagg interface xxx_attach() for attaching a laggport to a lagg interface and so on... If you want to programmatically attach, configure, modify, destroy lagg interfaces then you have choices like: shell scripts C code that performs the desired functions in the same way as ifconfig (userland) I can't see any immediate reason why you'd call functions like lagg_input() directly and you would have to be kernel-side to do so. What are you trying to achieve? Hope this helps! Dominic
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D35794.4030305>