From: Neal Cardwell <ncardwell@google.com>
To: Xin Guo <guoxin0309@gmail.com>
Cc: Neal Cardwell <ncardwell.sw@gmail.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Netdev <netdev@vger.kernel.org>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: [PATCH net 2/2] tcp: fix delayed ACKs for MSS boundary condition
Date: Sun, 1 Oct 2023 11:19:09 -0400 [thread overview]
Message-ID: <CADVnQymo2h4dYqeZQm9y5qqHoD1qrht9adLeuakFXzcKV5hyFQ@mail.gmail.com> (raw)
In-Reply-To: <CAMaK5_i-9dGgPtK9AErfjCaBVC72F=jzdQ968q9_TBLXoH3QBA@mail.gmail.com>
On Thu, Sep 28, 2023 at 11:56 AM Xin Guo <guoxin0309@gmail.com> wrote:
>
> Neal,
> thanks for your explanation,
> 1)when I read the patch, i cannot understood "if an app reads >1*MSS data",
> because in my view that "the app reads" mean that the copied data
> length from sk_receive_queue to user-space buffer
> in function tcp_recvmsg_locked(as example) when an app reads data from a socket,
> but for "tp->rcv_nxt - tp->rcv_wup > icsk->icsk_ack.rcv_mss ||"
> "tp->rcv_nxt - tp->rcv_wup" means that the received data length from
> last ack in the kernel for the sk,
> and not always the length of copied data to user-space buffer.
>
> 2) when we received two small packets(<1*MSS) in the kernel for the
> sk, the total length of the two packets may > 1*MSS.
Thanks for clarifying. Those are good points; the commit message could
and should be more precise when describing the existing logic in
tcp_cleanup_rbuf(). I have posted a v2 series with a more precise
commit message:
https://patchwork.kernel.org/project/netdevbpf/patch/20231001151239.1866845-2-ncardwell.sw@gmail.com/
best regards,
neal
next prev parent reply other threads:[~2023-10-01 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 15:15 [PATCH net 1/2] tcp: fix quick-ack counting to count actual ACKs of new data Neal Cardwell
2023-09-27 15:15 ` [PATCH net 2/2] tcp: fix delayed ACKs for MSS boundary condition Neal Cardwell
2023-09-28 8:53 ` Xin Guo
2023-09-28 14:38 ` Neal Cardwell
2023-09-28 15:56 ` Xin Guo
2023-10-01 15:19 ` Neal Cardwell [this message]
2023-10-02 5:33 ` Xin Guo
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=CADVnQymo2h4dYqeZQm9y5qqHoD1qrht9adLeuakFXzcKV5hyFQ@mail.gmail.com \
--to=ncardwell@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guoxin0309@gmail.com \
--cc=kuba@kernel.org \
--cc=ncardwell.sw@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).