[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51E2E36C.8030307@mojatatu.com>
Date: Sun, 14 Jul 2013 13:44:12 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: John Fastabend <john.r.fastabend@...el.com>
CC: Tom Herbert <therbert@...gle.com>,
John Fastabend <john.fastabend@...il.com>,
Stephen Hemminger <stephen@...workplumber.org>,
ben@...adent.org.uk,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
Linux Netdev List <netdev@...r.kernel.org>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Subject: Re: [RFC PATCH] net: add a rate_limit attribute to netdev_queue and
a rtnetlink
On 13-07-10 11:10 PM, John Fastabend wrote:
>
>> Will this be usable in the case that more than one queue shares a rate?
>
> Here I must not understand the question. Each queue has independent
> rate limiters. At least in the hardware supported by ixgbe. Maybe
> other hardware has a different implementation?
>
I think Tom might be alluding to scenarios where a rate (as a resource)
is shared by multiple ingress as well as egress interfaces (in your case
queues). This is a very popular use case with tc (in particular in
conjunction with IFB).
In such a case, the rate by itself would need to modeled as an indexable
attribute.
Some hardware (example modern broadcom switching chips, maybe yours)
are not capable; So the index would have local semantics as in your
case. But I know hardware that does support shared rates.
Maybe you could come up with IFLA_QUEUE_RATE_LOCAL vs
IFLA_QUEUE_RATE_GLOBAL which will encapsulate a global index
for the shared rate.
cheers,
jamal
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists