From: Stephen Hemminger <shemminger@vyatta.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
fubar@us.ibm.com, netdev@vger.kernel.org
Subject: Re: bonding...
Date: Thu, 3 Mar 2011 08:31:10 -0800 [thread overview]
Message-ID: <20110303083110.4e7f020c@nehalam> (raw)
In-Reply-To: <1299159991.4277.45.camel@localhost>
On Thu, 03 Mar 2011 13:46:31 +0000
Ben Hutchings <bhutchings@solarflare.com> wrote:
> On Wed, 2011-03-02 at 21:49 -0800, David Miller wrote:
> [...]
> > This is unacceptable, people are submitting multiple bonding patches
> > every single day now. It needs a clueful bonding person looking at
> > these submissions on a constant basis.
> [...]
>
> And preferably saying 'no' to most new features...
Agreed. It seems bonding has diverged from the standards and wants
to support every packet flow some user can think up.
next prev parent reply other threads:[~2011-03-03 16:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 5:49 bonding David Miller
2011-03-03 11:45 ` bonding Neil Horman
2011-03-03 16:04 ` bonding Andy Gospodarek
2011-03-03 17:24 ` bonding Jay Vosburgh
2011-03-03 20:30 ` bonding David Miller
2011-03-03 20:43 ` bonding Jay Vosburgh
2011-03-03 21:12 ` bonding Andy Gospodarek
2011-03-03 21:29 ` bonding David Miller
2011-03-03 20:59 ` bonding Andy Gospodarek
2011-03-03 13:46 ` bonding Ben Hutchings
2011-03-03 16:31 ` Stephen Hemminger [this message]
2011-03-03 16:52 ` bonding Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2014-02-11 13:53 Bonding Gustavo Pimentel
2014-02-11 14:15 ` Bonding Veaceslav Falico
2014-02-11 17:15 ` Bonding Gustavo Pimentel
2014-02-11 17:55 ` Bonding Jay Vosburgh
2014-02-11 18:22 ` Bonding Gustavo Pimentel
2009-09-16 8:44 bonding David Miller
2009-09-16 15:02 ` bonding Jay Vosburgh
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=20110303083110.4e7f020c@nehalam \
--to=shemminger@vyatta.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--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).