From: Jiri Pirko <jpirko@redhat•com>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: Andy Gospodarek <andy@greyhouse•net>,
David Miller <davem@davemloft•net>,
netdev@vger•kernel.org, bhutchings@solarflare•com,
shemminger@vyatta•com, fubar@us•ibm.com, tgraf@infradead•org,
ebiederm@xmission•com, mirqus@gmail•com, kaber@trash•net,
greearb@candelatech•com, jesse@nicira•com, fbl@redhat•com,
benjamin.poirier@gmail•com, jzupka@redhat•com,
ivecera@redhat•com
Subject: Re: [patch net-next V8] net: introduce ethernet teaming device
Date: Mon, 14 Nov 2011 22:37:49 +0100 [thread overview]
Message-ID: <20111114213749.GB2250@minipsycho> (raw)
In-Reply-To: <1321294672.2719.9.camel@edumazet-laptop>
Mon, Nov 14, 2011 at 07:17:52PM CET, eric.dumazet@gmail•com wrote:
>Le lundi 14 novembre 2011 à 12:31 -0500, Andy Gospodarek a écrit :
>
>> I'm a bit surprised by this. Not only is this new function currently
>> difficult to setup (it took me over an hour to go from a a fresh F16
>> install to one that had all the necessary libraries and tools to even
>> configure a team device for the first time), but I was able to cause an
>> Oops with v8 in only a few minutes of testing.
>>
>> I have no problem with this functionality as an add-on and possibly
>> future replacement to some of what currently exists with bonding, but it
>> seems like what is included in the initial support should should:
>>
>> 1. Not panic easily.
>> 2. Have userspace bits in place to actually test all the proposed kernel
>> code. (Jiri admits there is no way to verify the active-backup code).
>> 3. Have some known, published test results.
>>
>> I hope Jiri will reconsider having a separate team tree for the next few
>> weeks or months until these issues are worked out. I think the hard
>> work will pay off and it is close to being ready; it just doesn't seem
>> like it is right now.
>>
>
>Its marked EXPERIMENTAL, so probably some changes are expected before
>production mode :)
Exactly. The primary goal was to get this broader audience so people
use this and find bugs, like you did Andy :)
>
>
>
next prev parent reply other threads:[~2011-11-14 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 8:16 [patch net-next V8] net: introduce ethernet teaming device Jiri Pirko
2011-11-13 21:09 ` David Miller
2011-11-14 17:31 ` Andy Gospodarek
2011-11-14 18:17 ` Eric Dumazet
2011-11-14 21:37 ` Jiri Pirko [this message]
2011-11-14 17:18 ` Andy Gospodarek
2011-11-14 21:35 ` Jiri Pirko
2011-11-16 16:30 ` Jiri Pirko
2011-11-14 18:40 ` Rick Jones
2011-11-14 21:51 ` Jiri Pirko
2011-11-15 1:56 ` Andy Gospodarek
2011-11-15 17:22 ` Rick Jones
2011-11-15 18:35 ` Eric Dumazet
2011-11-16 23:01 ` Michał Mirosław
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=20111114213749.GB2250@minipsycho \
--to=jpirko@redhat$(echo .)com \
--cc=andy@greyhouse$(echo .)net \
--cc=benjamin.poirier@gmail$(echo .)com \
--cc=bhutchings@solarflare$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ebiederm@xmission$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=fbl@redhat$(echo .)com \
--cc=fubar@us$(echo .)ibm.com \
--cc=greearb@candelatech$(echo .)com \
--cc=ivecera@redhat$(echo .)com \
--cc=jesse@nicira$(echo .)com \
--cc=jzupka@redhat$(echo .)com \
--cc=kaber@trash$(echo .)net \
--cc=mirqus@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
--cc=tgraf@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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