Is it still possible to share ring buffers across multiple physical network
cards for zero-copy mode, or does the application need to take this into
account and perform a one-copy?
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman
Hello,
I wrote a kernel module [1] for a the fastd UDP tunneling protocol. Like
the if_tun it calls if_purgeaddrs() on destruction of interfaces. When I
delete IPFW rules a the same time the kernel runs into a deadlock. It
seems to be a general problem that also affects other network drivers.
The first is mostly cosmetic, it's just something I observed when
I turned on multicast debug to find the bug that the second patch
is for.
The second patch is a kludge and if anyone has a better fix, have
at it. :-) Note that it's also hard to provoke the bug. The only
way I know to observe it
On 4/16/2017 22:01, Ronald F. Guilmette wrote:
> Sorry, I -think- I know that answer to this question, but
> I'd prefer to ask and make sure, in case I have misunderstood
> things.
>
> I am aware that for any open socket, the kernel sets aside
> some amount of buffer space for that socket. (And y
Hi Navdeep
running "ifconfig up" and then "ifconfig promisc" works. Running
"ifconfig promisc" and then "ifconfig up" does not work. Running
"ifconfig up promisc" together does work. Running "ifconfig promisc up"
does not work.
The combination that does not work leaves the interface in a sta
