-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CBS Qdisc config fail with i218-LM #19
Comments
Yeah. I agree that the naming scheme doesn't make much sense, but Intel i218-LM is not based on Intel i210. It's even from another family, i.e. it uses the e1000e driver. I am sorry. |
Thanks for quick reply. But I am bit confuse. In datasheet of i218-LM, chapter 11 mentions support of 802.1AS "to ensure that synchronization So why do we need this Qdsic configuration ? Is it because AVB requires "higher level" of time sensitive criteria ? |
Oh, sorry. I must have written my last comment before coffee. I completely missed that you were only interested in
Just be aware, that as I said earlier, i218 doesn't have hardware support for offloading the other qdiscs. Sorry about the confusion. |
Hi, I tried to setup the qdsic mqprio using your command sample but it didn't work (RTNETLINK answers: Operation not supported). Have tried to change parameters but there is a lack of knowledge on my end to understand how to set things for my NIC. Especially about map priorities. man tc-mqprio didn't help to understand P0 -> P15 parameters. If you do you have any links or docs about this, feel free to share. I might input some confusion on my request too: |
Hi, maybe this could help you: |
Hi @maxmbed ,
Well, CBS and ETF are the ones that do the job regarding AVB - MQPRIO is there so that AVB traffic can be sent to the right qdisc (CBS and/or ETF). In theory, you can use only CBS or ETF, or both (as suggested in the AVB part of this tutorial), depends on your use case. |
Hi,
I am getting stuck at the configuration of CBS Qdisc as shown below:
I am using the intel i218-LM chip. Would it be possible the error is raised due to lack of support on i218-LM ?
System: Debian 10, kernel v4.19.0-10-amd64
The text was updated successfully, but these errors were encountered: