From: Jon Maloy <jmaloy@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, lvivier@redhat.com, dgibson@redhat.com
Subject: Re: [PATCH v9 0/2] Add support for SO_PEEK_OFF
Date: Mon, 15 Jul 2024 14:52:48 -0400 [thread overview]
Message-ID: <f9f903a5-6766-412d-857c-688042e2a000@redhat.com> (raw)
In-Reply-To: <20240715185803.37f940a5@elisabeth>
On 2024-07-15 12:58, Stefano Brivio wrote:
> On Fri, 12 Jul 2024 15:04:48 -0400
> Jon Maloy <jmaloy@redhat.com> wrote:
>
>> We add support for the SO_PEEK_OFF option, plus work around a kernel
>> bug discovered along the way.
>>
>> Jon Maloy (2):
>> tcp: leverage support of SO_PEEK_OFF socket option when available
>> tcp: handle shrunk window advertisemenst from guest
>>
>> tcp.c | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++++---
>> tcp.h | 3 +++
>> tcp_buf.c | 25 ++++++++++++++++------
>> 3 files changed, 81 insertions(+), 9 deletions(-)
> Applied!
Great! Finally. Thanks!
>
> I just s/advertisemenst/advertisements/ in 2/2, and fixed up the SHA of
> the buggy kernel commit... I guess d4317abf7160 is from your local tree?
I use net-next by old habit, and don't update it often. Maybe I should
change that.
> Upstream has e2142825c120.
>
///jon
prev parent reply other threads:[~2024-07-15 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 19:04 [PATCH v9 0/2] Add support for SO_PEEK_OFF Jon Maloy
2024-07-12 19:04 ` [PATCH v9 1/2] tcp: leverage support of SO_PEEK_OFF socket option when available Jon Maloy
2024-07-12 19:04 ` [PATCH v9 2/2] tcp: handle shrunk window advertisemenst from guest Jon Maloy
2024-07-15 0:34 ` David Gibson
2024-07-15 17:08 ` Stefano Brivio
2024-07-12 19:43 ` [PATCH v9 0/2] Add support for SO_PEEK_OFF Stefano Brivio
2024-07-15 16:58 ` Stefano Brivio
2024-07-15 18:52 ` Jon Maloy [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=f9f903a5-6766-412d-857c-688042e2a000@redhat.com \
--to=jmaloy@redhat.com \
--cc=dgibson@redhat.com \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).