On Fri, Aug 02, 2019 at 07:22:21PM +0000, Saeed Mahameed wrote: > On Fri, 2019-08-02 at 10:37 -0700, Alexei Starovoitov wrote: > > On Thu, Aug 1, 2019 at 6:30 PM Saeed Mahameed <sae...@mellanox.com> > > wrote: > > > From: Eli Cohen <e...@mellanox.com> > > > > > > Use the scheduling elements to implement ingress rate limiter on an > > > eswitch ports ingress traffic. Since the ingress of eswitch port is > > > the > > > egress of VF port, we control eswitch ingress by controlling VF > > > egress. > > > > Looks like the patch is only passing args to firmware which is doing > > the magic. > > Can you please describe what is the algorithm there? > > Is it configurable? > > Hi Alexei, > > I am not sure how much details you are looking for, but let me share > some of what i know: > > From a previous submission for legacy mode sriov vf bw limit, where we > introduced the FW configuration API and the legacy sriov use case: > https://patchwork.kernel.org/patch/9404655/ > > So basically the algorithm is Deficit Weighted Round Robin (DWRR) > between the agents, we can control BW allocation/weight of each agent > (vf vport).
commit log of this patch says nothing about DWRR. It is also not using any of the api that were provided by that earlier patch. what is going on?
