From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Vladimir Oltean <olteanv@gmail.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org,
Per Noergaard Christensen <per.christensen@prevas.dk>
Subject: Re: [PATCH net-next] net: dsa: microchip: add MRP software ring support
Date: Fri, 24 Nov 2023 09:28:13 +0100 [thread overview]
Message-ID: <36cbb7aa-1080-4fb8-88f7-2c8da82dd554@prevas.dk> (raw)
In-Reply-To: <20231122113537.o2fennnt2l2sri56@skbuf>
On 22/11/2023 12.35, Vladimir Oltean wrote:
> On Wed, Nov 22, 2023 at 12:20:06PM +0100, Rasmus Villemoes wrote:
>> From: Per Noergaard Christensen <per.christensen@prevas.dk>
>>
>> Add dummy functions that tells the MRP bridge instance to use
>> implemented software routines instead of hardware-offloading.
>>
>
> Could you please explain a bit the mechanics of this dummy implementation?
> Don't you need to set up any packet traps for MRP PDUs, to avoid
> forwarding them? What ring roles will work with the dummy implementation?
Hm, you're right, of course. We will have to check what went wrong in
our testing, we did believe we had it working, but that can't really be
true. So please ignore this for now, sorry for the noise.
Rasmus
prev parent reply other threads:[~2023-11-24 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 11:20 [PATCH net-next] net: dsa: microchip: add MRP software ring support Rasmus Villemoes
2023-11-22 11:35 ` Vladimir Oltean
2023-11-22 13:28 ` Horatiu Vultur
2023-11-24 8:28 ` Rasmus Villemoes [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=36cbb7aa-1080-4fb8-88f7-2c8da82dd554@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=per.christensen@prevas.dk \
--cc=woojung.huh@microchip.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).