On Fri, Apr 11, 2014 at 8:23 PM, hiren panchasara <
hiren.panchas...@gmail.com> wrote:
> On Fri, Apr 11, 2014 at 11:30 AM, Patrick Kelsey wrote:
> >
> > The output of netstat -Q shows IP dispatch is set to default, which is
> > direct (NETISR_DISPATCH_DIRECT). That means each IP packet will be
>
On Fri, Apr 11, 2014 at 11:30 AM, Patrick Kelsey wrote:
>
> The output of netstat -Q shows IP dispatch is set to default, which is
> direct (NETISR_DISPATCH_DIRECT). That means each IP packet will be
> processed on the same CPU that the Ethernet processing for that packet was
> performed on, so C
On Fri, Apr 11, 2014 at 2:48 AM, Adrian Chadd wrote:
> [snip]
>
> So, hm, the thing that comes to mind is the flowid. What's the various
> flowid's for flows? Are they all mapping to CPU 3 somehow
The output of netstat -Q shows IP dispatch is set to default, which is
direct (NETISR_DISPATCH_DIR
[snip]
So, hm, the thing that comes to mind is the flowid. What's the various
flowid's for flows? Are they all mapping to CPU 3 somehow?
-a
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, se
(Note: This may seem more like a rant than an actual problem report.)
I am on a stable-10ish box with igb0. Workload is mainly inbound nfs
traffic. About 2K connections at any point in time.
device igb # Intel PRO/1000 PCIE Server Gigabit Family
hw.igb.rxd: 4096
hw.igb.txd: 4
