What's the benefit in having a both an interrupt thread and task that
performs the same function? It seems to me that having two threads that do
the same job is what is making this so complicated.
___
freebsd-net@freebsd.org mailing list
http://lists.fre
The following reply was made to PR kern/176446; it has been noted by GNATS.
From: John Baldwin
To: "Charbon, Julien"
Cc: bug-follo...@freebsd.org,
"De La Gueronniere, Marc" ,
j...@freebsd.org
Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving
out-of-order packet process
Hello list,
I'm experiencing this odd behavior with 9.1 r24791 for amd64.
Find below exerpts from my rc.conf related to carp:
===
# production
ifconfig_carp22="inet 192.168.22.254/32 vhid 122 pass vrrp22 advskew 100"
ifconfig_carp32="inet 192.168.32.254/32 vhid 132 pass vrrp32 advskew 100"
clo
I have been looking at the FreeBSD congestion control code and had some
questions on the SACK enabled code flow .
With SACK the congestion window is retained as 1 MSS when the Fast Retransmit
is exited and Fast Recovery is entered,so cwnd growth seems to be much slower
than slow start, as
On Thu, Mar 14, 2013 at 12:44:33PM +0600, Eugene M. Zheganin wrote:
> Hi.
>
> On 13.03.2013 07:57, YongHyeon PYUN wrote:
> >
> > If your controller supports ASF/IPMI access please apply r248226
> > to stable/8 and let me know whether that makes any difference.
> > I believe ignoring ASF/IPMI firmw
