s set by the user to indicate
whether this interface is enabled or not. I.e. IFF_RUNNING set by system,
IFF_UP set by user. This however, doesn't seem to be the case in all drivers
though. I would be very pleased if someone could clarify the issue further.
Please correct me if I'm totally wr
[snip]
> >For sure the "de" driver might have its own problems,
> >but i think a lot of packet drops also depend on the card
> >not being properly set for full duplex (which can
> >cause collisions and lots of drops).
>
>
> You should initially test mono-directional in a controlled
> environme
[snip]
> >triggers every second and steals too much cpu. So my
> question is, how can I
> >decrease this routing delay?
> Were you loading the interface, or just passing nominal
> streams? What pps
> did you pass through the box? Most likely the "delays" are
> only seen when
> the machine is
I've performed a routing test between a FreeBSD box and a Linux box. I
measured the latency and the result was not what I had expected. Both
systems had the peak at 100 us (microseconds), but whereas the Linux box had
_no_ packet over 200 us, the FreeBSD box delayed some packets up to 2 ms!
Lookin
I'm trying to convert a PCI network interface device driver to a KLD module.
However, the driver is depending on a pseudo-device and the pseudo-device is
in turn dependent on the device driver. How do I specify dependencies
between KLD modules and what type of module shall they be? Are there any
d
5 matches
Mail list logo
