From: David Miller <davem@davemloft.net>
To: pabeni@redhat.com
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us,
john.fastabend@gmail.com, mst@redhat.com
Subject: Re: [PATCH net-next 0/2] sched: refactor NOLOCK qdiscs
Date: Thu, 17 May 2018 13:06:45 -0400 (EDT) [thread overview]
Message-ID: <20180517.130645.233025265779233333.davem@davemloft.net> (raw)
In-Reply-To: <cover.1526392746.git.pabeni@redhat.com>
From: Paolo Abeni <pabeni@redhat.com>
Date: Tue, 15 May 2018 16:24:35 +0200
> With the introduction of NOLOCK qdiscs, pfifo_fast performances in the
> uncontended scenario degraded measurably, especially after the commit
> eb82a9944792 ("net: sched, fix OOO packets with pfifo_fast").
>
> This series restore the pfifo_fast performances in such scenario back the
> previous level, mainly reducing the number of atomic operations required to
> perform the qdisc_run() call. Even performances in the contended scenario
> increase measurably.
>
> Note: This series is on top of:
>
> sched: manipulate __QDISC_STATE_RUNNING in qdisc_run_* helpers
Series applied, thank you.
prev parent reply other threads:[~2018-05-17 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 14:24 [PATCH net-next 0/2] sched: refactor NOLOCK qdiscs Paolo Abeni
2018-05-15 14:24 ` [PATCH net-next 1/2] sched: replace __QDISC_STATE_RUNNING bit with a spin lock Paolo Abeni
2018-05-15 14:24 ` [PATCH net-next 2/2] pfifo_fast: drop unneeded additional lock on dequeue Paolo Abeni
2018-05-15 20:17 ` Michael S. Tsirkin
2018-05-16 7:56 ` Paolo Abeni
2018-05-16 9:57 ` Paolo Abeni
2018-05-16 14:24 ` Michael S. Tsirkin
2018-05-17 17:06 ` David Miller [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=20180517.130645.233025265779233333.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiyou.wangcong@gmail.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).