From: Wally Zhao <wallyzhao@gmail.com>
To: vyasevich@gmail.com, nhorman@tuxdriver.com,
marcelo.leitner@gmail.com, davem@davemloft.net,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: wally.zhao@nokia-sbell.com, Wally Zhao <wallyzhao@gmail.com>
Subject: [PATCH] sctp: set ooo_okay properly for Transmit Packet Steering
Date: Wed, 30 Oct 2019 12:07:17 -0400 [thread overview]
Message-ID: <1572451637-14085-1-git-send-email-wallyzhao@gmail.com> (raw)
Unlike tcp_transmit_skb,
sctp_packet_transmit does not set ooo_okay explicitly,
causing unwanted Tx queue switching when multiqueue is in use;
Tx queue switching may cause out-of-order packets.
Change sctp_packet_transmit to allow Tx queue switching only for
the first in flight packet, to avoid unwanted Tx queue switching.
Signed-off-by: Wally Zhao <wallyzhao@gmail.com>
---
net/sctp/output.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/net/sctp/output.c b/net/sctp/output.c
index dbda7e7..5ff75cc 100644
--- a/net/sctp/output.c
+++ b/net/sctp/output.c
@@ -626,6 +626,10 @@ int sctp_packet_transmit(struct sctp_packet *packet, gfp_t gfp)
/* neighbour should be confirmed on successful transmission or
* positive error
*/
+
+ /* allow switch tx queue only for the first in flight pkt */
+ head->ooo_okay = asoc->outqueue.outstanding_bytes == 0;
+
if (tp->af_specific->sctp_xmit(head, tp) >= 0 &&
tp->dst_pending_confirm)
tp->dst_pending_confirm = 0;
--
1.8.3.1
next reply other threads:[~2019-10-30 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 16:07 Wally Zhao [this message]
2019-10-30 13:24 ` [PATCH] sctp: set ooo_okay properly for Transmit Packet Steering Marcelo Ricardo Leitner
2019-10-30 15:54 ` Wei Zhao
2019-10-30 18:35 ` Marcelo Ricardo Leitner
2019-10-30 19:03 ` Eric Dumazet
2019-10-31 1:11 ` Wei Zhao
2019-11-04 8:46 ` [sctp] 327fecdaf3: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2019-11-04 13:25 ` Marcelo Ricardo Leitner
2019-11-04 14:14 ` Wei Zhao
2019-11-04 14:49 ` Marcelo Ricardo Leitner
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=1572451637-14085-1-git-send-email-wallyzhao@gmail.com \
--to=wallyzhao@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.com \
--cc=wally.zhao@nokia-sbell.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).