From: Andrew Lunn <andrew@lunn.ch>
To: John Fastabend <john.fastabend@gmail.com>
Cc: Simon Horman <simon.horman@netronome.com>,
Jiri Pirko <jiri@resnulli.us>,
Premkumar Jonnala <pjonnala@broadcom.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Hardware capabilities and bonding offload
Date: Wed, 18 Nov 2015 15:05:12 +0100 [thread overview]
Message-ID: <20151118140512.GC6123@lunn.ch> (raw)
In-Reply-To: <564BCD12.4010804@gmail.com>
> To be honest though this is more of an argument in theory versus
> some existing management agent I know of today. If you need to do
> bonding type X in your network and the particular switch doesn't support
> it I'm not even sure what the mgmt layer is going to do. Maybe just
> put the switch offline for that network segment.
>
> If you leave the sw bit out in the first iteration I'm OK with that
> we can easily add it when we have software that needs it.
Taking a step back...
Have we defined a consistent way for signalling:
1) Failed to offload to the hardware, because the hardware cannot do
what you requested.
2) Do this in software, rather than trying and failing to offload to
hardware.
At least in DSA, we return EOPNOTSUP for 1).
Andrew
next prev parent reply other threads:[~2015-11-18 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 9:29 Hardware capabilities and bonding offload Premkumar Jonnala
2015-11-16 15:30 ` Jiri Pirko
2015-11-16 16:10 ` John Fastabend
2015-11-17 22:03 ` Simon Horman
2015-11-18 0:57 ` John Fastabend
2015-11-18 14:05 ` Andrew Lunn [this message]
2015-11-18 14:29 ` Jiri Pirko
2015-11-18 14:50 ` Andrew Lunn
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=20151118140512.GC6123@lunn.ch \
--to=andrew@lunn.ch \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pjonnala@broadcom.com \
--cc=simon.horman@netronome.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).