public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Jason Xing <kerneljasonxing@gmail.com>
To: Jon Maloy <jmaloy@redhat.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org, passt-dev@passt.top,
	sbrivio@redhat.com, lvivier@redhat.com, dgibson@redhat.com,
	eric.dumazet@gmail.com, edumazet@google.com
Subject: Re: [PATCH 2/2] selftests: add selftest for tcp SO_PEEK_OFF support
Date: Sun, 1 Sep 2024 08:32:57 +0800	[thread overview]
Message-ID: <CAL+tcoC-CTaD-_68Nee+CoysJV7zYojqqgU8Y+Nq6RkQRuv=DA@mail.gmail.com> (raw)
In-Reply-To: <9f4dd14d-fbe3-4c61-b04c-f0e6b8096d7b@redhat.com>

Hello Jon,

On Tue, Aug 27, 2024 at 3:58 AM Jon Maloy <jmaloy@redhat.com> wrote:
>
>
>
> On 2024-08-23 19:44, Jason Xing wrote:
> > Hello Jon,
> >
> > On Sat, Aug 24, 2024 at 5:19 AM <jmaloy@redhat.com> wrote:
> >> From: Jon Maloy <jmaloy@redhat.com>
> >>
> >> We add a selftest to check that the new feature added in
> >> commit 05ea491641d3 ("tcp: add support for SO_PEEK_OFF socket option")
> >> works correctly.
> >>
> >> Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
> >> Tested-by: Stefano Brivio <sbrivio@redhat.com>
> >> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
> > Thanks for working on this. Sorry that I just noticed I missed your
> > previous reply :(
> There is still the ditto UDP selftest to be done ;-)

The reason why I didn't respond at that time is because I was unsure
if I had enough time to finish it. Now it's time.

After digging into this, there will be a lot of duplicated code if I
write a new one named like "udp_so_peek_off". I think adjusting your
tcp_so_peek_off.c to complete the UDP part is just fine. Of course,
tcp_so_peek_off.c will be renamed :)

I will post one later to see if it's reasonable...

Thanks,
Jason

      reply	other threads:[~2024-09-01  0:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 21:19 [PATCH 0/2] Adding SO_PEEK_OFF for TCPv6 jmaloy
2024-08-23 21:19 ` [PATCH 1/2] tcp: add SO_PEEK_OFF socket option tor TCPv6 jmaloy
2024-08-23 23:51   ` Jason Xing
2024-08-26 22:25     ` Jon Maloy
2024-08-24  8:55   ` Eric Dumazet
2024-08-23 21:19 ` [PATCH 2/2] selftests: add selftest for tcp SO_PEEK_OFF support jmaloy
2024-08-23 23:44   ` Jason Xing
2024-08-26 19:58     ` Jon Maloy
2024-09-01  0:32       ` Jason Xing [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='CAL+tcoC-CTaD-_68Nee+CoysJV7zYojqqgU8Y+Nq6RkQRuv=DA@mail.gmail.com' \
    --to=kerneljasonxing@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dgibson@redhat.com \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=netdev@vger.kernel.org \
    --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).