Hi Hans,
Yes, we understand that piece of code.
But Panasas wants this change to MFC to 10.3. This issue is not seen in 11.
Would that happen? I have not seen acknowledgement of this issue or
confirmation of MFC to 10.3. That information will help us plan.
Regards,
LN
On Wed, Jan 13, 2016 at 6:0
Hi Team,
I am seeing a crash with 10.1 stable which is not seen in 11-CURRENT.
This is with lagg port operations, the below simple sequence of cmds cause
system crash.
ifconfig lagg0 create
ifconfig lagg0 laggproto failover laggport le0
ifconfig lagg0 /* crash here */
See below for the backtraces
Hi FreeBSD Team,
We have been working on LACP timeout tunable to help expedite link failure
propagation through a IOCtl interface.
The changes have been tested and review is in progress.
The phabricator link is https://reviews.freebsd.org/D3300
We would kindly appreciate if the changes can
ologies.com, Lewis, Fred, 'Tallam, Sreen'
Hi LN,
You also need to teach `ifconfig' how to toggle this new setting. See
sbin/ifconfig/iflagg.c:lagg_cmds[]
and how the other LACP options are handled. (Thanks to Genesys on #bsdcode
for pointing that out.)
Also, please confi
Hi FreeBSD team,
In FreeBSD-10 and in Current, by default LACP supports only long timeout.
FreeBSD does not provide the way to configure LACP timeout period.
We made code changes for LACP Fast-timeout (Using IOCTL, both GET / SET) on
FreeBSD-11.
And we were able to successfully test the oper
Hi FreeBSD folks,
I am part of Panasas and working on evaluating IXL over FreeBSD
[11-CURRENT] on Intel Taylor Pass platform for our next product.
In that regard, while evaluating performance, we found the Tx performance
to be very poor. We found it to be so because the tx interrupts are spread
ov
Hi FreeBSD Team!
We seem to have found a problem to Tx performance.
We found that the tx handling is spread on all CPUs causing probably cache
trashing resulting in poor performance.
But once we used cpuset to bind interrupt thread and iperf process to the same
CPU, performance was close to
