From: Breno Leitao <leitao@debian.org>
To: Eric Dumazet <edumazet@google.com>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] net: dql: Optimize stall information population
Date: Mon, 8 Apr 2024 09:25:39 -0700 [thread overview]
Message-ID: <ZhQagwjRHBNsQbIw@gmail.com> (raw)
In-Reply-To: <CANn89iLhi365XA2-5vQwf+ELRYEep=NFSHxVAE=v0cXjpANh4w@mail.gmail.com>
On Thu, Apr 04, 2024 at 06:36:00PM +0200, Eric Dumazet wrote:
> On Thu, Apr 4, 2024 at 5:00 PM Breno Leitao <leitao@debian.org> wrote:
> >
> > When Dynamic Queue Limit (DQL) is set, it always populate stall
> > information through dql_queue_stall(). However, this information is
> > only necessary if a stall threshold is set, stored in struct
> > dql->stall_thrs.
> >
> > dql_queue_stall() is cheap, but not free, since it does have memory
> > barriers and so forth.
> >
> > Do not call dql_queue_stall() if there is no stall threshold set, and
> > save some CPU cycles.
> >
> > Signed-off-by: Breno Leitao <leitao@debian.org>
> > ---
> > include/linux/dynamic_queue_limits.h | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/linux/dynamic_queue_limits.h b/include/linux/dynamic_queue_limits.h
> > index 9980df0b7247..869afb800ea1 100644
> > --- a/include/linux/dynamic_queue_limits.h
> > +++ b/include/linux/dynamic_queue_limits.h
> > @@ -137,7 +137,9 @@ static inline void dql_queued(struct dql *dql, unsigned int count)
> >
> > dql->num_queued += count;
> >
> > - dql_queue_stall(dql);
> > + /* Only populate stall information if the threshold is set */
> > + if (READ_ONCE(dql->stall_thrs))
> > + dql_queue_stall(dql);
>
> Note that this field is not in the first cache line of 'struct dql',
> we will have some false sharing.
>
> Perhaps we could copy it in a hole of the first cache line (used by producers).
That is a good point. Let me move stall_thrs to the first hole.
Thanks
prev parent reply other threads:[~2024-04-08 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 14:59 [PATCH net-next 0/3] net: dqs: optimize if stall threshold is not set Breno Leitao
2024-04-04 14:59 ` [PATCH net-next 1/3] net: dql: Avoid calling BUG() when WARN() is enough Breno Leitao
2024-04-04 14:59 ` [PATCH net-next 2/3] net: dql: Separate queue function responsibilities Breno Leitao
2024-04-04 14:59 ` [PATCH net-next 3/3] net: dql: Optimize stall information population Breno Leitao
2024-04-04 16:36 ` Eric Dumazet
2024-04-08 16:25 ` Breno Leitao [this message]
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=ZhQagwjRHBNsQbIw@gmail.com \
--to=leitao@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.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).