On 8/27/19 10:53 PM, Dave Taht wrote:
>
> Although this is very cool, I think in this case the OP is being
> a router, not server?
This mechanism is generic. EDT has not been designed for servers only.
One HTB class (with one associated qdisc per leaf) per rate limiter
does not scale, and con
On Sun, Aug 25, 2019 at 11:47 PM Eric Dumazet wrote:
>
>
>
> On 8/25/19 7:52 PM, Cong Wang wrote:
> > On Wed, Aug 21, 2019 at 11:00 PM Akshat Kakkar
> > wrote:
> >>
> >> On Thu, Aug 22, 2019 at 3:37 AM Cong Wang wrote:
> I am using ipset + iptables to classify and not filters. Besides, if
On Sun, 18 Aug 2019 00:34:33 +0530
Akshat Kakkar wrote:
> My goal is not just to make as many classes as possible, but also to
> use them to do rate limiting per ip per server. Say, I have a list of
> 1 IPs and more than 100 servers. So simply if I want few IPs to
> get speed of says 1Mbps pe
Eric Dumazet writes:
> On 8/25/19 7:52 PM, Cong Wang wrote:
>> On Wed, Aug 21, 2019 at 11:00 PM Akshat Kakkar wrote:
>>>
>>> On Thu, Aug 22, 2019 at 3:37 AM Cong Wang wrote:
> I am using ipset + iptables to classify and not filters. Besides, if
> tc is allowing me to define qdisc -> cl
On 8/25/19 7:52 PM, Cong Wang wrote:
> On Wed, Aug 21, 2019 at 11:00 PM Akshat Kakkar wrote:
>>
>> On Thu, Aug 22, 2019 at 3:37 AM Cong Wang wrote:
I am using ipset + iptables to classify and not filters. Besides, if
tc is allowing me to define qdisc -> classes -> qdsic -> classes
>
On Wed, Aug 21, 2019 at 11:00 PM Akshat Kakkar wrote:
>
> On Thu, Aug 22, 2019 at 3:37 AM Cong Wang wrote:
> > > I am using ipset + iptables to classify and not filters. Besides, if
> > > tc is allowing me to define qdisc -> classes -> qdsic -> classes
> > > (1,2,3 ...) sort of structure (ie lik
On Thu, Aug 22, 2019 at 3:37 AM Cong Wang wrote:
> > I am using ipset + iptables to classify and not filters. Besides, if
> > tc is allowing me to define qdisc -> classes -> qdsic -> classes
> > (1,2,3 ...) sort of structure (ie like the one shown in ascii tree)
> > then how can those lowest chil
On Sat, Aug 17, 2019 at 12:04 PM Akshat Kakkar wrote:
> I am using ipset + iptables to classify and not filters. Besides, if
> tc is allowing me to define qdisc -> classes -> qdsic -> classes
> (1,2,3 ...) sort of structure (ie like the one shown in ascii tree)
> then how can those lowest child c
>> If your goal is merely having as many classes as you can, then yes.
My goal is not just to make as many classes as possible, but also to
use them to do rate limiting per ip per server. Say, I have a list of
1 IPs and more than 100 servers. So simply if I want few IPs to
get speed of says 1M
On Sat, Aug 17, 2019 at 11:54 PM Cong Wang wrote:
>
> On Sat, Aug 17, 2019 at 5:46 AM Akshat Kakkar wrote:
> >
> > I agree that it is because of 16bit of minor I'd of class which
> > restricts it to 64K.
> > Point is, can we use multilevel qdisc and classes to extend it to more
> > no. of classes
On Sat, Aug 17, 2019 at 5:46 AM Akshat Kakkar wrote:
>
> I agree that it is because of 16bit of minor I'd of class which
> restricts it to 64K.
> Point is, can we use multilevel qdisc and classes to extend it to more
> no. of classes i.e. to more than 64K classes
If your goal is merely having as
I agree that it is because of 16bit of minor I'd of class which
restricts it to 64K.
Point is, can we use multilevel qdisc and classes to extend it to more
no. of classes i.e. to more than 64K classes
One scheme can be like
100: root qdisc
On Fri, Aug 16, 2019 at 5:49 AM Akshat Kakkar wrote:
>
> I want to have around 1 Million htb tc classes.
> The simple structure of htb tc class, allow having only 64K classes at once.
This is probably due the limit of class ID which is 16bit for minor.
> But, it is possible to make it more hier
I want to have around 1 Million htb tc classes.
The simple structure of htb tc class, allow having only 64K classes at once.
But, it is possible to make it more hierarchical using hierarchy of
qdisc and classes.
For this I tried something like this
tc qdisc add dev eno2 root handle 100: htb
tc cla
14 matches
Mail list logo
