From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Zh-yuan Ye <ye.zh-yuan@socionext.com>, netdev@vger.kernel.org
Cc: okamoto.satoru@socionext.com, kojima.masahisa@socionext.com,
Zh-yuan Ye <ye.zh-yuan@socionext.com>
Subject: Re: [PATCH net v2] net: cbs: Fix software cbs to consider packet sending time
Date: Mon, 23 Mar 2020 12:39:37 -0700 [thread overview]
Message-ID: <87tv2edfnq.fsf@intel.com> (raw)
In-Reply-To: <20200323061709.1881-1-ye.zh-yuan@socionext.com>
Hi,
Zh-yuan Ye <ye.zh-yuan@socionext.com> writes:
> Currently the software CBS does not consider the packet sending time
> when depleting the credits. It caused the throughput to be
> Idleslope[kbps] * (Port transmit rate[kbps] / |Sendslope[kbps]|) where
> Idleslope * (Port transmit rate / (Idleslope + |Sendslope|)) = Idleslope
> is expected. In order to fix the issue above, this patch takes the time
> when the packet sending completes into account by moving the anchor time
> variable "last" ahead to the send completion time upon transmission and
> adding wait when the next dequeue request comes before the send
> completion time of the previous packet.
Yeah, this improves (a lot) the accuracy of the software mode when
dealing with larger packets:
| Idleslope (packet size) | Old (bps) | New (bps) |
|-------------------------+-----------+-----------|
| 500mbps (100bytes) | 528M | 492M |
| 500mbps (1500bytes) | 622M | 499M |
| 1mbps (100bytes) | 1007k | 1006k |
| 1mbps (1500bytes) | 1010k | 1010k |
(Sorry for the mess of units)
So, when the comments from Jakub are addressed:
Reviewed-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cheers,
--
Vinicius
prev parent reply other threads:[~2020-03-23 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 6:17 [PATCH net v2] net: cbs: Fix software cbs to consider packet sending time Zh-yuan Ye
2020-03-23 17:47 ` Jakub Kicinski
2020-03-23 19:39 ` Vinicius Costa Gomes [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=87tv2edfnq.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=kojima.masahisa@socionext.com \
--cc=netdev@vger.kernel.org \
--cc=okamoto.satoru@socionext.com \
--cc=ye.zh-yuan@socionext.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).