From: Andrew Lunn <andrew@lunn.ch>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Jonathan Corbet <corbet@lwn.net>, Jiri Pirko <jiri@nvidia.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] net: ti: am65-cpsw-nuss: Add devlink support
Date: Thu, 3 Dec 2020 15:18:38 +0100 [thread overview]
Message-ID: <20201203141838.GE2333853@lunn.ch> (raw)
In-Reply-To: <cc7fe740-1002-f1b9-8136-e1ba60cf2541@ti.com>
> We don't want to enable HW based switch support unless explicitly
> asked by user.
This is the key point. Why? Does individual ports when passed through
the switch not work properly? Does it add extra latency/jitter?
Please justify this.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Jonathan Corbet <corbet@lwn.net>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jiri Pirko <jiri@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] net: ti: am65-cpsw-nuss: Add devlink support
Date: Thu, 3 Dec 2020 15:18:38 +0100 [thread overview]
Message-ID: <20201203141838.GE2333853@lunn.ch> (raw)
In-Reply-To: <cc7fe740-1002-f1b9-8136-e1ba60cf2541@ti.com>
> We don't want to enable HW based switch support unless explicitly
> asked by user.
This is the key point. Why? Does individual ports when passed through
the switch not work properly? Does it add extra latency/jitter?
Please justify this.
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-03 14:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 8:20 [PATCH 0/4] net: ti: am65-cpsw-nuss: Add switchdev driver Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 8:20 ` [PATCH 1/4] net: ti: am65-cpsw-nuss: Add devlink support Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 15:50 ` Andrew Lunn
2020-11-30 15:50 ` Andrew Lunn
2020-12-03 8:40 ` Vignesh Raghavendra
2020-12-03 8:40 ` Vignesh Raghavendra
2020-12-03 14:18 ` Andrew Lunn [this message]
2020-12-03 14:18 ` Andrew Lunn
2020-12-03 16:22 ` Grygorii Strashko
2020-12-03 16:22 ` Grygorii Strashko
2020-11-30 8:20 ` [PATCH 2/4] net: ti: am65-cpsw-nuss: Add netdevice notifiers Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 8:20 ` [PATCH 3/4] net: ti: am65-cpsw-nuss: Add switchdev support Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 17:20 ` Andrew Lunn
2020-11-30 17:20 ` Andrew Lunn
2020-12-03 13:49 ` Vignesh Raghavendra
2020-12-03 13:49 ` Vignesh Raghavendra
2020-11-30 8:20 ` [PATCH 4/4] docs: networking: ti: Add driver doc for AM65 NUSS switch driver Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
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=20201203141838.GE2333853@lunn.ch \
--to=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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.