From: patchwork-bot+netdevbpf@kernel.org
To: Hoang Huu Le <hoang.h.le@dektech.com.au>
Cc: jmaloy@redhat.com, ying.xue@windriver.com, netdev@vger.kernel.org
Subject: Re: [net 1/2] tipc: re-configure queue limit for broadcast link
Date: Fri, 16 Oct 2020 21:30:03 +0000 [thread overview]
Message-ID: <160288380340.31566.9245323917252134913.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201016023119.5833-1-hoang.h.le@dektech.com.au>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Fri, 16 Oct 2020 09:31:18 +0700 you wrote:
> The queue limit of the broadcast link is being calculated base on initial
> MTU. However, when MTU value changed (e.g manual changing MTU on NIC
> device, MTU negotiation etc.,) we do not re-calculate queue limit.
> This gives throughput does not reflect with the change.
>
> So fix it by calling the function to re-calculate queue limit of the
> broadcast link.
>
> [...]
Here is the summary with links:
- [net,1/2] tipc: re-configure queue limit for broadcast link
https://git.kernel.org/netdev/net/c/75cee397ae6f
- [net,2/2] tipc: fix incorrect setting window for bcast link
https://git.kernel.org/netdev/net/c/ec78e31852c9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-10-16 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 2:31 [net 1/2] tipc: re-configure queue limit for broadcast link Hoang Huu Le
2020-10-16 2:31 ` [net 2/2] tipc: fix incorrect setting window for bcast link Hoang Huu Le
2020-10-16 21:18 ` [net 1/2] tipc: re-configure queue limit for broadcast link Jakub Kicinski
2020-10-16 21:30 ` patchwork-bot+netdevbpf [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=160288380340.31566.9245323917252134913.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=hoang.h.le@dektech.com.au \
--cc=jmaloy@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ying.xue@windriver.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).