From: David Miller <davem@davemloft.net>
To: horms@verge.net.au
Cc: netdev@vger.kernel.org, fubar@us.ibm.com
Subject: Re: bonding: propagation of offload settings
Date: Wed, 24 Nov 2010 12:27:36 -0800 (PST) [thread overview]
Message-ID: <20101124.122736.200378471.davem@davemloft.net> (raw)
In-Reply-To: <20101030025435.GF12842@verge.net.au>
From: Simon Horman <horms@verge.net.au>
Date: Sat, 30 Oct 2010 11:54:35 +0900
> It seems to me that from a user point of view it may make more sense to:
>
> a) propagate settings from the master to the slaves and;
> b) possibly disallow setting the slaves directly
Yeah, good question.
Propagation from master to slave(s) would have difficult semantics.
If any of the slave changes fail (f.e. unsupported feature or memory
allocation failure) we'd have to unwind all of the slaves which did
accept the change without error.
What if the unwind operation fails, due to lack of resources? A lot
of state would thus need to be tracked to support this reasonably.
However we pretty much have to respect whatever changes get made
directly to the slaves, since the master must at all times claim
support for only the lowest common denominator, feature wise, amongst
that master's slaves.
prev parent reply other threads:[~2010-11-24 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 2:54 bonding: propagation of offload settings Simon Horman
2010-11-24 20:27 ` David Miller [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=20101124.122736.200378471.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=horms@verge.net.au \
--cc=netdev@vger.kernel.org \
/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).