Home > OS >  About double VLAN packet cannot be assigned to the network card queue problem
About double VLAN packet cannot be assigned to the network card queue problem

Time:10-02


Nic is 82599 10 g network card, network card is multi-queue
Isn't the question now is when the call flow with VLAN or with a single VLAN, network card received packet queue can be more balanced,
If with double VLAN, network card only rx_queue_0 queue queue can receive more data
Because network card driver based on packet 4 tuple hash algorithms on different queue, if processing is not the will to the default queue 0
Now suspected to be network card driver cannot handle double VLAN,
Online have a similar problem, https://sourceforge.net/p/e1000/mailman/message/24456397/

Is there anyone master know how to solve the problem of the

CodePudding user response:

Ace has to understand the problem?

CodePudding user response:

No exception: we have to configure the vlan - tag on the centos6, switch port is no configuration access mode; Deployed more than one hundred units, temporary not found similar problems,
Question: a vlan - tag is the function on the second floor? Look at the

CodePudding user response:

refer to the original poster benluobobo response:
nics are 82599 10 g network card, network card is multi-queue
Isn't the question now is when the call flow with VLAN or with a single VLAN, network card received packet queue can be more balanced,
If with double VLAN, network card only rx_queue_0 queue queue can receive more data
Because network card driver based on packet 4 tuple hash algorithms on different queue, if processing is not the will to the default queue 0
Now suspected to be network card driver cannot handle double VLAN,
Online have a similar problem, https://sourceforge.net/p/e1000/mailman/message/24456397/

Is there anyone master know how to solve the problem of the



Or add my qq chat line is: 652107095

CodePudding user response:

That just estimate, suggest to see the spec or with Intel 82599 relevant personnel to consult,

CodePudding user response:

Bugs encountered the same problem, has been on the same nuclear qinq processing, no shunt, do you now to solve this problem, or know where is the main problem
  • Related