lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMiKbPs6eMkVzUEgu-GWqTd7x56CRtuqo5J9+xdUZEjjAA@mail.gmail.com>
Date:	Wed, 11 Mar 2015 22:11:07 +0200
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	John Fastabend <john.r.fastabend@...el.com>
Cc:	Or Gerlitz <ogerlitz@...lanox.com>,
	"David S. Miller" <davem@...emloft.net>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Amir Vadai <amirv@...lanox.com>,
	Ido Shamay <idos@...lanox.com>,
	Matan Barak <matanb@...lanox.com>
Subject: Re: [PATCH net-next 1/3] net: Add max rate tx queue attribute

On Wed, Mar 11, 2015, John Fastabend <john.r.fastabend@...el.com> wrote:
> On 03/11/2015 06:14 AM, Or Gerlitz wrote:

>> This adds a tx_maxrate attribute to the tx queue sysfs entry allowing
>> for max-rate limiting. Along with DCB-ETS and BQL this provides another
>> knob to tune queue performance. The limit units are Mbps.
>>
>> By default it is disabled. To disable the rate limitation after it
>> has been set for a queue, it should be set to zero.

>>  include/linux/netdevice.h |    9 ++++++
>>  net/core/net-sysfs.c      |   70 +++++++++++++++++++++++++++++++++++++--------

> hmm I'm not sure sysfs is entirely the correct interface although it is convenient.

Very convenient indeed, and we use it for bunch of other tunables
(xps, affinities and such). So I would vote for keeping it.

>  Did you consider porting to netlink? To be honest I can't remember why
>  I didn't do it netlink to start with. I think at the time
> I was more interested in the controller, feedback loop aspect. Basically
> I was dynamically managing the rate limiters across NICs from an agent to
> try and manage some types of congestion.

Sure, but we can add later netlink interface on top of the basic patch
that defines the ndo. I assume you refer to rtnetlink and the
changelink callback? can a driver instantiate it w.o having
newlink/dellink bindings?
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ