From: Jakub Kicinski <kuba@kernel.org>
To: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"nhorman@redhat.com" <nhorman@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Bowers, AndrewX" <andrewx.bowers@intel.com>,
"sassmann@redhat.com" <sassmann@redhat.com>,
"Tieman, Henry W" <henry.w.tieman@intel.com>
Subject: Re: [net-next 05/16] ice: Add support for tunnel offloads
Date: Thu, 5 Mar 2020 17:22:45 -0800 [thread overview]
Message-ID: <20200305172245.37a4b3d2@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <4fd3bf3a8d473af7a40831b63e126f3dd6959950.camel@intel.com>
On Fri, 6 Mar 2020 01:08:45 +0000 Nguyen, Anthony L wrote:
> > > + status = ice_create_tunnel(&pf->hw, tnl_type, port);
> > > + if (status == ICE_ERR_ALREADY_EXISTS)
> > > + dev_dbg(ice_pf_to_dev(pf), "port %d already exists in
> > > UDP tunnels list\n",
> > > + port);
> > > + else if (status == ICE_ERR_OUT_OF_RANGE)
> > > + netdev_err(netdev, "Max tunneled UDP ports reached,
> > > port %d not added\n",
> > > + port);
> >
> > error is probably a little much for resource exhaustion since it's
> > not
> > going to cause any problem other than a slow down?
>
> Correct, just a slow down. A warning then or did you prefer a dbg?
No preference.
next prev parent reply other threads:[~2020-03-06 1:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 23:21 [net-next 00/16][pull request] 100GbE Intel Wired LAN Driver Updates 2020-03-04 Jeff Kirsher
2020-03-04 23:21 ` [net-next 01/16] ice: Cleanup unneeded parenthesis Jeff Kirsher
2020-03-04 23:21 ` [net-next 02/16] iavf: Enable support for up to 16 queues Jeff Kirsher
2020-03-04 23:21 ` [net-next 03/16] ice: allow bigger VFs Jeff Kirsher
2020-03-04 23:21 ` [net-next 04/16] ice: Improve clarity of prints and variables Jeff Kirsher
2020-03-04 23:21 ` [net-next 05/16] ice: Add support for tunnel offloads Jeff Kirsher
2020-03-05 2:46 ` Jakub Kicinski
2020-03-06 1:08 ` Nguyen, Anthony L
2020-03-06 1:22 ` Jakub Kicinski [this message]
2020-03-04 23:21 ` [net-next 06/16] ice: Fix removing driver while bare-metal VFs pass traffic Jeff Kirsher
2020-03-04 23:21 ` [net-next 07/16] ice: Display Link detected via Ethtool in safe mode Jeff Kirsher
2020-03-04 23:21 ` [net-next 08/16] ice: Fix corner case when switching from IEEE to CEE Jeff Kirsher
2020-03-04 23:21 ` [net-next 09/16] ice: renegotiate link after FW DCB on Jeff Kirsher
2020-03-04 23:21 ` [net-next 10/16] ice: Correct setting VLAN pruning Jeff Kirsher
2020-03-04 23:21 ` [net-next 11/16] ice: Increase mailbox receive queue length to maximum Jeff Kirsher
2020-03-04 23:21 ` [net-next 12/16] ice: fix use of deprecated strlcpy() Jeff Kirsher
2020-03-04 23:21 ` [net-next 13/16] ice: Fix format specifier Jeff Kirsher
2020-03-04 23:21 ` [net-next 14/16] ice: Use EOPNOTSUPP instead of ENOTSUPP Jeff Kirsher
2020-03-04 23:21 ` [net-next 15/16] ice: use variable name more descriptive than type Jeff Kirsher
2020-03-04 23:21 ` [net-next 16/16] ice: fix incorrect size description of ice_get_nvm_version Jeff Kirsher
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=20200305172245.37a4b3d2@kicinski-fedora-PC1C0HJN \
--to=kuba@kernel.org \
--cc=andrewx.bowers@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=henry.w.tieman@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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).