igb(4) Pondering a bind to cpu patch
- From: Sean Bruno <seanbru@xxxxxxxxxxxxx>
- Date: Tue, 24 Apr 2012 17:11:07 -0700
Scenario I've just seen:
8 core machine
2 igb(4) interfaces
igb0:0 --> cpu0
igb0:1 --> cpu1
igb0:2 --> cpu2
igb0:3 --> cpu3
igb1:0 --> cpu0
igb1:1 --> cpu1
igb1:2 --> cpu2
igb1:3 --> cpu3
I suspect, that we need a static global to keep track of what cpu last
was last bound to a queue. My patch does do this, but I don't know if
its the right thing.
Since I'm doing multiple interfaces, I need to make sure I don't
schedule a queue to a non existent cpu, so take a modulo of the counter
and the number of cpus in the box.
Perhaps not the most elegant solution, but its a thing?
freebsd-net@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: Some performance measurements on the FreeBSD network stack
- Next by Date: Re: igb(4) Pondering a bind to cpu patch
- Previous by thread: LLA (Link local address) in FreeBSD route command
- Next by thread: Re: igb(4) Pondering a bind to cpu patch