From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
dsahern@kernel.org, willemb@google.com, netdev@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Subject: Re: [PATCH net-next v2 2/2] net: make SOF_TIMESTAMPING_RX_SOFTWARE feature per socket
Date: Thu, 29 Aug 2024 19:14:35 -0700 [thread overview]
Message-ID: <20240829191435.739154ef@kernel.org> (raw)
In-Reply-To: <CAL+tcoCXTwarrWpaZ8adVz9cV0FsROTBRHJS5v3YOtE0jJD+ZQ@mail.gmail.com>
On Fri, 30 Aug 2024 08:40:47 +0800 Jason Xing wrote:
> In this case, we expect to control whether we can report the rx
> timestamp in this function. But we also need to handle the egress
> path, or else reporting the tx timestamp will fail. Egress path and
> ingress path will finally call sock_recv_timestamp(). We have to
> distinguish them. Errqueue is a good indicator to reflect the flow
> direction.
That is better, FWIW, thanks
next prev parent reply other threads:[~2024-08-30 2:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 16:01 [PATCH net-next v2 0/2] timestamp: control SOF_TIMESTAMPING_RX_SOFTWARE feature per socket Jason Xing
2024-08-28 16:01 ` [PATCH net-next v2 1/2] tcp: make " Jason Xing
2024-08-29 14:16 ` Willem de Bruijn
2024-08-29 15:34 ` Jason Xing
2024-08-28 16:01 ` [PATCH net-next v2 2/2] net: " Jason Xing
2024-08-29 10:02 ` Jason Xing
2024-08-29 14:21 ` Willem de Bruijn
2024-08-29 15:38 ` Jason Xing
2024-08-29 19:29 ` Jakub Kicinski
2024-08-30 0:40 ` Jason Xing
2024-08-30 2:14 ` Jakub Kicinski [this message]
2024-08-29 14:14 ` [PATCH net-next v2 0/2] timestamp: control " Willem de Bruijn
2024-08-29 15:27 ` Jason Xing
2024-08-29 16:23 ` Willem de Bruijn
2024-08-29 17:45 ` Jason Xing
2024-08-29 18:15 ` Willem de Bruijn
2024-08-29 18:31 ` Jason Xing
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=20240829191435.739154ef@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.