netdev - Re: [PATCH] net: make CONFIG_BQL actually end user configurable

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] [day] [month] [year] [list]

Message-ID: <CA+mtBx9kZc+Ovrohbffxe=be6zehNneCXQsH7HrgYELmtfLptA@mail.gmail.com>
Date:	Mon, 5 Mar 2012 21:57:40 -0800
From:	Tom Herbert <therbert@...gle.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Dave Taht <dave.taht@...il.com>, davem@...emloft.net,
	eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH] net: make CONFIG_BQL actually end user configurable

>> 1) There is no way to tell if a driver has it actually enabled or not
>> at run time.
>
> In a similar vein, I was interested in a (quick) way to tell if a
> driver has it actually enabled *correctly*.  I'd coded up the basic
> changes for a common PPC NIC, but I was then left wondering what I
> could use as a quick high-water-mark to see if I'd really managed
> to implement it correctly via some level of real run-time testing.
>
The sysfs variables should be good to view the operation and effects
of BQL.  To disable BQL (at least limit checking) "echo max >
limit_min" should be sufficient.

It is true there is no way to determine that BQL is implement for a
device, the sysfs variables are always created.  If it is
unimplemented then inflight and limit variables are always zero.

> If we want to get driver authors involved in adding support to their
> favourite hardware, some description of a basic sanity test would
> probably be a worthwhile description to have.

That would be good.  The best window into BQL is the sysfs variables
(inflight and limit).  Setting zero or max to limit_min should impact
the number of queued bytes being reported.  ("watch cat *" in tx-0I'm
still intending to get the document on BQL out, the sanity check would
be good to describe there I think.

Thanks,
Tom
--
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