From: Breno Leitao <leitao@debian.org>
To: Eric Dumazet <edumazet@google.com>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, Johannes Berg <johannes.berg@intel.com>,
Amritha Nambiar <amritha.nambiar@intel.com>
Subject: Re: [PATCH net-next] net: sysfs: Do not create sysfs for non BQL device
Date: Thu, 15 Feb 2024 05:11:26 -0800 [thread overview]
Message-ID: <Zc4NfrT3qEOMPAPP@gmail.com> (raw)
In-Reply-To: <CANn89iJsdvjsbcYv_Re5HHvmY=P7Sq6ewV_sdQuWTAFtOPoKbw@mail.gmail.com>
On Thu, Feb 15, 2024 at 01:47:47PM +0100, Eric Dumazet wrote:
> On Thu, Feb 15, 2024 at 12:28 PM Breno Leitao <leitao@debian.org> wrote:
> >
> > Creation of sysfs entries is expensive, mainly for workloads that
> > constantly creates netdev and netns often.
> >
> > Do not create BQL sysfs entries for devices that don't need,
> > basically those that do not have a real queue, i.e, devices that has
> > NETIF_F_LLTX and IFF_NO_QUEUE, such as `lo` interface.
> >
> > This will remove the /sys/class/net/eth0/queues/tx-X/byte_queue_limits/
> > directory for these devices.
> >
> > In the example below, eth0 has the `byte_queue_limits` directory but not
> > `lo`.
> >
> > # ls /sys/class/net/lo/queues/tx-0/
> > traffic_class tx_maxrate tx_timeout xps_cpus xps_rxqs
> >
> > # ls /sys/class/net/eth0/queues/tx-0/byte_queue_limits/
> > hold_time inflight limit limit_max limit_min
> >
> > Suggested-by: Eric Dumazet <edumazet@google.com>
> > Signed-off-by: Breno Leitao <leitao@debian.org>
> > ---
> > net/core/net-sysfs.c | 23 ++++++++++++++++++-----
> > 1 file changed, 18 insertions(+), 5 deletions(-)
> >
> > diff --git a/net/core/net-sysfs.c b/net/core/net-sysfs.c
> > index a09d507c5b03..c79bc11a0347 100644
> > --- a/net/core/net-sysfs.c
> > +++ b/net/core/net-sysfs.c
> > @@ -1417,6 +1417,15 @@ static ssize_t bql_show_inflight(struct netdev_queue *queue,
> > return sysfs_emit(buf, "%u\n", dql->num_queued - dql->num_completed);
> > }
> >
> > +static bool netdev_uses_bql(struct net_device *dev)
>
> const struct net_device *dev
Thanks. I will update and incorporate it in a v2 (that I am planning to
send tomorrow).
next prev parent reply other threads:[~2024-02-15 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 11:27 [PATCH net-next] net: sysfs: Do not create sysfs for non BQL device Breno Leitao
2024-02-15 12:47 ` Eric Dumazet
2024-02-15 13:11 ` Breno Leitao [this message]
2024-02-15 15:24 ` 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=Zc4NfrT3qEOMPAPP@gmail.com \
--to=leitao@debian.org \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).