From: patchwork-bot+netdevbpf@kernel.org
To: Song Yoong Siang <yoong.siang.song@intel.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, willemb@google.com,
florian.bezdeka@siemens.com, donald.hunter@gmail.com,
corbet@lwn.net, bjorn@kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com,
andrew+netdev@lunn.ch, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, jdamato@fastly.com,
sdf@fomichev.me, xuanzhuo@linux.alibaba.com,
almasrymina@google.com, danielj@nvidia.com, andrii@kernel.org,
eddyz87@gmail.com, mykolal@fb.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, faizal.abdul.rahim@linux.intel.com,
yong.liang.choong@linux.intel.com, zdenek.bouska@siemens.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
intel-wired-lan@lists.osuosl.org, xdp-hints@xdp-project.net
Subject: Re: [PATCH bpf-next v12 0/5] xsk: TX metadata Launch Time support
Date: Fri, 21 Feb 2025 01:40:40 +0000 [thread overview]
Message-ID: <174010204026.1539943.5735764109259382582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250216093430.957880-1-yoong.siang.song@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Sun, 16 Feb 2025 17:34:25 +0800 you wrote:
> This series expands the XDP TX metadata framework to allow user
> applications to pass per packet 64-bit launch time directly to the kernel
> driver, requesting launch time hardware offload support. The XDP TX
> metadata framework will not perform any clock conversion or packet
> reordering.
>
> Please note that the role of Tx metadata is just to pass the launch time,
> not to enable the offload feature. Users will need to enable the launch
> time hardware offload feature of the device by using the respective
> command, such as the tc-etf command.
>
> [...]
Here is the summary with links:
- [bpf-next,v12,1/5] xsk: Add launch time hardware offload support to XDP Tx metadata
https://git.kernel.org/bpf/bpf-next/c/ca4419f15abd
- [bpf-next,v12,2/5] selftests/bpf: Add launch time request to xdp_hw_metadata
https://git.kernel.org/bpf/bpf-next/c/6164847e5403
- [bpf-next,v12,3/5] net: stmmac: Add launch time support to XDP ZC
https://git.kernel.org/bpf/bpf-next/c/04f64dea1364
- [bpf-next,v12,4/5] igc: Refactor empty frame insertion for launch time support
https://git.kernel.org/bpf/bpf-next/c/f9b53bb13923
- [bpf-next,v12,5/5] igc: Add launch time support to XDP ZC
https://git.kernel.org/bpf/bpf-next/c/d7c3a7ff7502
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Song Yoong Siang <yoong.siang.song@intel.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, willemb@google.com,
florian.bezdeka@siemens.com, donald.hunter@gmail.com,
corbet@lwn.net, bjorn@kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com,
andrew+netdev@lunn.ch, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, jdamato@fastly.com,
sdf@fomichev.me, xuanzhuo@linux.alibaba.com,
almasrymina@google.com, danielj@nvidia.com, andrii@kernel.org,
eddyz87@gmail.com, mykolal@fb.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, faizal.abdul.rahim@linux.intel.com,
yong.liang.choong@linux.intel.com, zdenek.bouska@siemens.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
intel-wired-lan@lists.osuosl.org, xdp-hints@xdp-project.net
Subject: Re: [Intel-wired-lan] [PATCH bpf-next v12 0/5] xsk: TX metadata Launch Time support
Date: Fri, 21 Feb 2025 01:40:40 +0000 [thread overview]
Message-ID: <174010204026.1539943.5735764109259382582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250216093430.957880-1-yoong.siang.song@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Sun, 16 Feb 2025 17:34:25 +0800 you wrote:
> This series expands the XDP TX metadata framework to allow user
> applications to pass per packet 64-bit launch time directly to the kernel
> driver, requesting launch time hardware offload support. The XDP TX
> metadata framework will not perform any clock conversion or packet
> reordering.
>
> Please note that the role of Tx metadata is just to pass the launch time,
> not to enable the offload feature. Users will need to enable the launch
> time hardware offload feature of the device by using the respective
> command, such as the tc-etf command.
>
> [...]
Here is the summary with links:
- [bpf-next,v12,1/5] xsk: Add launch time hardware offload support to XDP Tx metadata
https://git.kernel.org/bpf/bpf-next/c/ca4419f15abd
- [bpf-next,v12,2/5] selftests/bpf: Add launch time request to xdp_hw_metadata
https://git.kernel.org/bpf/bpf-next/c/6164847e5403
- [bpf-next,v12,3/5] net: stmmac: Add launch time support to XDP ZC
https://git.kernel.org/bpf/bpf-next/c/04f64dea1364
- [bpf-next,v12,4/5] igc: Refactor empty frame insertion for launch time support
https://git.kernel.org/bpf/bpf-next/c/f9b53bb13923
- [bpf-next,v12,5/5] igc: Add launch time support to XDP ZC
https://git.kernel.org/bpf/bpf-next/c/d7c3a7ff7502
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-02-21 1:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 9:34 [PATCH bpf-next v12 0/5] xsk: TX metadata Launch Time support Song Yoong Siang
2025-02-16 9:34 ` [Intel-wired-lan] " Song Yoong Siang
2025-02-16 9:34 ` [PATCH bpf-next v12 1/5] xsk: Add launch time hardware offload support to XDP Tx metadata Song Yoong Siang
2025-02-16 9:34 ` [Intel-wired-lan] " Song Yoong Siang
2025-02-20 22:17 ` Jakub Kicinski
2025-02-20 22:17 ` [Intel-wired-lan] " Jakub Kicinski
2025-02-16 9:34 ` [PATCH bpf-next v12 2/5] selftests/bpf: Add launch time request to xdp_hw_metadata Song Yoong Siang
2025-02-16 9:34 ` [Intel-wired-lan] " Song Yoong Siang
2025-02-16 9:34 ` [PATCH bpf-next v12 3/5] net: stmmac: Add launch time support to XDP ZC Song Yoong Siang
2025-02-16 9:34 ` [Intel-wired-lan] " Song Yoong Siang
2025-02-16 9:34 ` [PATCH bpf-next v12 4/5] igc: Refactor empty frame insertion for launch time support Song Yoong Siang
2025-02-16 9:34 ` [Intel-wired-lan] " Song Yoong Siang
2025-02-16 9:34 ` [PATCH bpf-next v12 5/5] igc: Add launch time support to XDP ZC Song Yoong Siang
2025-02-16 9:34 ` [Intel-wired-lan] " Song Yoong Siang
2025-03-07 13:25 ` Bouska, Zdenek
2025-03-07 13:25 ` [Intel-wired-lan] " Bouska, Zdenek
2025-03-07 14:20 ` Song, Yoong Siang
2025-03-07 14:20 ` [Intel-wired-lan] " Song, Yoong Siang
2025-03-10 8:08 ` Bouska, Zdenek
2025-03-10 8:08 ` [Intel-wired-lan] " Bouska, Zdenek
2025-02-21 1:40 ` patchwork-bot+netdevbpf [this message]
2025-02-21 1:40 ` [Intel-wired-lan] [PATCH bpf-next v12 0/5] xsk: TX metadata Launch Time support patchwork-bot+netdevbpf
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=174010204026.1539943.5735764109259382582.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=faizal.abdul.rahim@linux.intel.com \
--cc=florian.bezdeka@siemens.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdamato@fastly.com \
--cc=joabreu@synopsys.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jonathan.lemon@gmail.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=martin.lau@linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=willemb@google.com \
--cc=xdp-hints@xdp-project.net \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yong.liang.choong@linux.intel.com \
--cc=yonghong.song@linux.dev \
--cc=yoong.siang.song@intel.com \
--cc=zdenek.bouska@siemens.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.