From: Florian Fainelli <f.fainelli@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Breno Leitao <leitao@debian.org>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, horms@kernel.org,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH net-next v2] net: sysfs: Do not create sysfs for non BQL device
Date: Fri, 16 Feb 2024 10:41:52 -0800 [thread overview]
Message-ID: <0e0ba573-1ae0-4a4b-8286-fdbc8dbe7639@gmail.com> (raw)
In-Reply-To: <20240216092905.4e2d3c7c@hermes.local>
On 2/16/24 09:29, Stephen Hemminger wrote:
> On Fri, 16 Feb 2024 01:41:52 -0800
> Breno Leitao <leitao@debian.org> wrote:
>
>> +static bool netdev_uses_bql(const struct net_device *dev)
>> +{
>> + if (dev->features & NETIF_F_LLTX ||
>> + dev->priv_flags & IFF_NO_QUEUE)
>> + return false;
>> +
>> + return IS_ENABLED(CONFIG_BQL);
>> +}
>
> Various compilers will warn about missing parens in that expression.
> It is valid but mixing & and || can be bug trap.
>
> if ((dev->features & NETIF_F_LLTX) || (dev->priv_flags & IFF_NO_QUEUE))
> return false;
>
> Not all drivers will be using bql, it requires driver to have that code.
> So really it means driver could be using BQL.
> Not sure if there is a way to find out if driver has the required BQL bits.
There is not a feature flag to be keying off if that is what you are
after, you would need to audit the drivers and see whether they make
calls to netdev_tx_sent_queue(), netdev_tx_reset_queue(),
netdev_tx_completed_queue().
I suppose you might be able to programmatically extract that information
by looking at whether a given driver object file has a reference to
dql_{reset,avail,completed} or do that at the source level, whichever is
easier.
--
Florian
next prev parent reply other threads:[~2024-02-16 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 9:41 Breno Leitao
2024-02-16 17:29 ` Stephen Hemminger
2024-02-16 18:41 ` Florian Fainelli [this message]
2024-02-16 18:45 ` Eric Dumazet
2024-02-19 9:46 ` Breno Leitao
2024-06-09 4:47 ` Jason Xing
2024-06-09 13:19 ` Jason Xing
2024-02-19 10:46 ` Simon Horman
2024-02-19 20:16 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e0ba573-1ae0-4a4b-8286-fdbc8dbe7639@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®