From: Vladimir Oltean <olteanv@gmail.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>,
irusskikh@marvell.com, andrew+netdev@lunn.ch, bharat@chelsio.com,
ayush.sawal@chelsio.com, UNGLinuxDriver@microchip.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, sgoutham@marvell.com,
willemb@google.com, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next v1 4/4] net: lan966x: generate software timestamp just before the doorbell
Date: Thu, 8 May 2025 15:40:47 +0300 [thread overview]
Message-ID: <20250508124047.xyhrabkxsbhceujv@skbuf> (raw)
In-Reply-To: <CAL+tcoBrB05QSTQjcCS7=W3GRTC5MeGoKv=inxtQHPvmYcmVyA@mail.gmail.com>
On Thu, May 08, 2025 at 08:22:39PM +0800, Jason Xing wrote:
> Thanks for the kind reply.
>
> It looks like how to detect depends on how the bpf prog is written?
> Mostly depends on how the writer handles this data part. Even though
> we don't guarantee on how to ask users/admins to write/adjust their
> bpf codes, it's not that convenient for them if this patch is applied,
> to be frank. I'm not pushing you to accept this patch, just curious on
> "how and why". Now I can guess why you're opposed to it....
The BPF program is not user-generated, it is run in the context of the
function you're moving.
skb_tx_timestamp()
-> skb_clone_tx_timestamp()
-> classify()
-> ptp_classify_raw()
-> bpf_prog_run(ptp_insns, skb)
next prev parent reply other threads:[~2025-05-08 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 3:33 [PATCH net-next v1 0/4] misc drivers' sw timestamp changes Jason Xing
2025-05-08 3:33 ` [PATCH net-next v1 1/4] net: atlantic: generate software timestamp just before the doorbell Jason Xing
2025-05-08 3:33 ` [PATCH net-next v1 2/4] net: cxgb4: " Jason Xing
2025-05-08 3:33 ` [PATCH net-next v1 3/4] net: stmmac: " Jason Xing
2025-05-08 3:33 ` [PATCH net-next v1 4/4] net: lan966x: " Jason Xing
2025-05-08 7:07 ` Horatiu Vultur
2025-05-08 8:40 ` Jason Xing
2025-05-08 9:41 ` Horatiu Vultur
2025-05-08 12:22 ` Jason Xing
2025-05-08 12:40 ` Vladimir Oltean [this message]
2025-05-08 14:16 ` Jason Xing
2025-05-08 14:21 ` Vladimir Oltean
2025-05-12 7:22 ` Horatiu Vultur
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=20250508124047.xyhrabkxsbhceujv@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=ayush.sawal@chelsio.com \
--cc=bharat@chelsio.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=horms@kernel.org \
--cc=irusskikh@marvell.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.com \
--cc=willemb@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