From: "Malladi, Meghana" <m-malladi@ti.com>
To: Diogo Ivo <diogo.ivo@siemens.com>,
Roger Quadros <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>, <krzysztof.kozlowski@linaro.org>,
<dan.carpenter@linaro.org>, <schnelle@linux.ibm.com>,
<glaroque@baylibre.com>, <rdunlap@infradead.org>,
<jan.kiszka@siemens.com>, <john.fastabend@gmail.com>,
<hawk@kernel.org>, <daniel@iogearbox.net>, <ast@kernel.org>,
<srk@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH net-next v2 1/3] net: ti: icssg-prueth: Use page_pool API for RX buffer allocation
Date: Tue, 18 Feb 2025 17:58:27 +0530 [thread overview]
Message-ID: <94425bfd-7f2b-4fc4-86f8-a56e56173d22@ti.com> (raw)
In-Reply-To: <c8bdd93d-5690-4b8a-819f-853756b57a71@siemens.com>
Hi Diogo,
On 2/18/2025 5:54 PM, Diogo Ivo wrote:
> Hi Meghana, On 2/18/25 10: 10 AM, Malladi, Meghana wrote: > On 2/12/2025
> 7: 26 PM, Roger Quadros wrote: >> Can we get rid of SKB entirely from
> the management channel code? >> The packet received on this channel is
> never passed to
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source
> of this email and know the content is safe.
> Report Suspicious
> <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/G3vK!
> uvdgfB3F_Ow7QIXEnBKj3ybYT8I9yL0CM5RLkel44YW99zMeqk_TnCBkOwR0q45N5dLjtBz49EalJyUJ1-U1lPk6DIBve_3-$>
> ZjQcmQRYFpfptBannerEnd
>
> Hi Meghana,
>
> On 2/18/25 10:10 AM, Malladi, Meghana wrote:
>> On 2/12/2025 7:26 PM, Roger Quadros wrote:
>>> Can we get rid of SKB entirely from the management channel code?
>>> The packet received on this channel is never passed to user space so
>>> I don't see why SKB is required.
>>>
>>
>> Yes I do agree with you on the fact the SKB here is not passed to the
>> network stack, hence this is redundant. But honestly I am not sure how
>> that can be done, because the callers of this function access skb->data
>> from the skb which is returned and the same can't be done with page (how
>> to pass the same data using page?)
>> Also as you are aware we are not currently supporting SR1 devices
>> anymore, hence I don't have any SR1 devices handy to test these changes
>> and ensure nothing is broken if I remove SKB entirely.
>
> I have some SR1 devices available and would be happy to test these
> proposed changes in case they are feasible.
>
That's awesome. Once the changes have been aligned with Roger, I will
share the changes with you for testing before posting v3. Thanks for
your support.
> Best regards,
> Diogo
>
next prev parent reply other threads:[~2025-02-18 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 10:33 [PATCH net-next v2 0/3] Add native mode XDP support Meghana Malladi
2025-02-10 10:33 ` [PATCH net-next v2 1/3] net: ti: icssg-prueth: Use page_pool API for RX buffer allocation Meghana Malladi
2025-02-12 13:56 ` Roger Quadros
2025-02-18 10:10 ` Malladi, Meghana
2025-02-18 12:24 ` Diogo Ivo
2025-02-18 12:28 ` Malladi, Meghana [this message]
2025-02-24 13:20 ` Roger Quadros
2025-02-10 10:33 ` [PATCH net-next v2 2/3] net: ti: icssg-prueth: introduce and use prueth_swdata struct for SWDATA Meghana Malladi
2025-02-12 14:12 ` Roger Quadros
2025-02-18 11:02 ` Malladi, Meghana
2025-02-10 10:33 ` [PATCH net-next v2 3/3] net: ti: icssg-prueth: Add XDP support Meghana Malladi
2025-02-11 18:39 ` kernel test robot
2025-02-11 22:20 ` kernel test robot
2025-02-12 16:03 ` Roger Quadros
2025-02-18 18:29 ` Malladi, Meghana
2025-02-18 16:02 ` [PATCH net-next v2 0/3] Add native mode " Jesper Dangaard Brouer
2025-02-18 17:55 ` Malladi, Meghana
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=94425bfd-7f2b-4fc4-86f8-a56e56173d22@ti.com \
--to=m-malladi@ti.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=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=glaroque@baylibre.com \
--cc=hawk@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=john.fastabend@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).