public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Eric Dumazet <edumazet@google.com>
To: Jon Maloy <jmaloy@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
	kuba@kernel.org, passt-dev@passt.top, sbrivio@redhat.com,
	lvivier@redhat.com, dgibson@redhat.com, netdev@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [PATCH v3] tcp: add support for SO_PEEK_OFF
Date: Fri, 16 Feb 2024 11:55:47 +0100	[thread overview]
Message-ID: <CANn89iJHDdF=bbtbs_WkmPG7Km1YNO9miuGW6SGOm-CtJQzM5w@mail.gmail.com> (raw)
In-Reply-To: <6a9f5dec-eb0c-51ef-0911-7345f50e08f0@redhat.com>

On Fri, Feb 16, 2024 at 11:13 AM Jon Maloy <jmaloy@redhat.com> wrote:

>
> There is also the following alternative:
>
> if (flags & MSG_PEEK)
>        sk_peek_offset_fwd(sk, used);
> else if (flags & MSG_TRUNC)
>        sk_peek_offset_bwd(sk, used);
>
> This is the way we use it, and probably the typical usage.
> It would force a user to drain the receive queue with MSG_TRUNC whenever he is using
> MSG_PEEK_OFF, but I don't really see that as a limitation.
>
> Anyway, if Paolo's suggestion solves the problem this shouldn't be necessary.

I think the suggestion to move sk_peek_off came from my first message
on this thread ;)
 "We need to move sk_peek_off in a better location before we accept this patch."

Anyway, a complete reorg of 'struct sock' was overdue, I am working on it.

  parent reply	other threads:[~2024-02-16 10:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 22:12 [PATCH v3] tcp: add support for SO_PEEK_OFF jmaloy
2024-02-11 23:17 ` Stefano Brivio
2024-02-13 10:49 ` Paolo Abeni
2024-02-13 12:24   ` Eric Dumazet
2024-02-13 13:02     ` Paolo Abeni
2024-02-13 13:34       ` Eric Dumazet
2024-02-13 15:28         ` Paolo Abeni
2024-02-13 15:49           ` Eric Dumazet
2024-02-13 18:39             ` Paolo Abeni
2024-02-13 19:31               ` Eric Dumazet
     [not found]                 ` <20687849-ec5c-9ce5-0a18-cc80f5b64816@redhat.com>
2024-02-15 17:41                   ` Paolo Abeni
2024-02-15 17:46                     ` Eric Dumazet
2024-02-15 22:24                       ` Jon Maloy
2024-02-16  9:14                         ` Paolo Abeni
2024-02-16  9:21                           ` Eric Dumazet
     [not found]                             ` <6a9f5dec-eb0c-51ef-0911-7345f50e08f0@redhat.com>
2024-02-16 10:55                               ` Eric Dumazet [this message]
2024-02-19  2:02                               ` David Gibson
2024-02-13 23:34             ` David Gibson
2024-02-14  3:41               ` Eric Dumazet
2024-02-15  3:16                 ` David Gibson
2024-02-15  3:21               ` David Gibson
2024-02-15  9:15                 ` Eric Dumazet

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='CANn89iJHDdF=bbtbs_WkmPG7Km1YNO9miuGW6SGOm-CtJQzM5w@mail.gmail.com' \
    --to=edumazet@google.com \
    --cc=davem@davemloft.net \
    --cc=dgibson@redhat.com \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=lvivier@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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).