From: Diogo Ivo <diogo.ivo@siemens.com>
To: Meghana Malladi <m-malladi@ti.com>,
rogerq@kernel.org, danishanwar@ti.com, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
andrew+netdev@lunn.ch
Cc: bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
u.kleine-koenig@baylibre.com, matthias.schiffer@ew.tq-group.com,
dan.carpenter@linaro.org, schnelle@linux.ibm.com,
glaroque@baylibre.com, macro@orcam.me.uk,
john.fastabend@gmail.com, hawk@kernel.org, daniel@iogearbox.net,
ast@kernel.org, srk@ti.com, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH net-next v3 0/3] net: ti: icssg-prueth: Add native mode XDP support
Date: Mon, 24 Feb 2025 13:35:14 +0000 [thread overview]
Message-ID: <b437f359-912f-4b9f-8de1-9c1122fee26e@siemens.com> (raw)
In-Reply-To: <20250224110102.1528552-1-m-malladi@ti.com>
Hi Meghana,
On 2/24/25 11:00 AM, Meghana Malladi wrote:
> This series adds native XDP support using page_pool.
> XDP zero copy support is not included in this patch series.
>
> Patch 1/3: Replaces skb with page pool for Rx buffer allocation
> Patch 2/3: Adds prueth_swdata struct for SWDATA for all swdata cases
> Patch 3/3: Introduces native mode XDP support
>
> v2: https://lore.kernel.org/all/20250210103352.541052-1-m-malladi@ti.com/
>
Just wanted to let you know that while I don't have access to the SR1.0
devices at the moment I will have access to them later this week, so I
will test these changes then.
Best regards,
Diogo
prev parent reply other threads:[~2025-02-24 14:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 11:00 [PATCH net-next v3 0/3] net: ti: icssg-prueth: Add native mode XDP support Meghana Malladi
2025-02-24 11:01 ` [PATCH net-next v3 1/3] net: ti: icssg-prueth: Use page_pool API for RX buffer allocation Meghana Malladi
2025-02-24 14:20 ` Roger Quadros
2025-03-03 11:16 ` Malladi, Meghana
2025-02-24 11:01 ` [PATCH net-next v3 2/3] net: ti: icssg-prueth: introduce and use prueth_swdata struct for SWDATA Meghana Malladi
2025-02-26 10:29 ` Dan Carpenter
2025-03-03 11:49 ` [EXTERNAL] " Malladi, Meghana
2025-02-27 12:27 ` Roger Quadros
2025-03-03 11:23 ` Malladi, Meghana
2025-02-24 11:01 ` [PATCH net-next v3 3/3] net: ti: icssg-prueth: Add XDP support Meghana Malladi
2025-02-26 10:49 ` Dan Carpenter
2025-03-03 12:06 ` [EXTERNAL] " Malladi, Meghana
2025-03-03 12:31 ` Dan Carpenter
2025-03-03 13:36 ` Malladi, Meghana
2025-03-03 14:08 ` Dan Carpenter
2025-03-05 9:23 ` Malladi, Meghana
2025-03-05 9:31 ` Dan Carpenter
2025-02-27 15:37 ` Roger Quadros
2025-03-03 11:36 ` Malladi, Meghana
2025-02-24 13:35 ` Diogo Ivo [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=b437f359-912f-4b9f-8de1-9c1122fee26e@siemens.com \
--to=diogo.ivo@siemens.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=daniel@iogearbox.net \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=glaroque@baylibre.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-malladi@ti.com \
--cc=macro@orcam.me.uk \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=srk@ti.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vigneshr@ti.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