From: Eric Dumazet <eric.dumazet@gmail.com>
To: "George B." <georgeb@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Network multiqueue question
Date: Fri, 16 Apr 2010 06:53:53 +0200 [thread overview]
Message-ID: <1271393633.16881.3606.camel@edumazet-laptop> (raw)
In-Reply-To: <j2gb65cae941004152100je5a3c3c9lba9e96ecb95bf04c@mail.gmail.com>
Le jeudi 15 avril 2010 à 21:00 -0700, George B. a écrit :
> On Thu, Apr 15, 2010 at 10:47 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
>
>
> > Since this bothers me a bit, I will probably work on this in a near
> > future. (adding real multiqueue capability and RCU to bonding fast
> > paths)
> >
> > Ref: http://permalink.gmane.org/gmane.linux.network/152987
>
> That would be great and you would have my sincere thanks.. And if
> anyone is interested, what we do is take a pair of "top of rack"
> switches and cluster them together so they appear as one switch.
> Configure a LAG consisting of a port on each physical switch to a pair
> of bonded interfaces on the server and use mode 2 bonding. In normal
> operation, both interfaces are active. Should one switch experience a
> power or interface failure, the server sees one of the interfaces fail
> but just keeps working on the remaining interface. There is no
> "failover" event going on.
>
What kind of traffic do your machines manage exactly ?
On server, you use two ports of the same kind (same number of queues) ?
next prev parent reply other threads:[~2010-04-16 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 16:58 Network multiqueue question George B.
2010-04-15 17:47 ` Eric Dumazet
2010-04-15 18:09 ` Jay Vosburgh
2010-04-15 18:41 ` Eric Dumazet
2010-04-16 3:54 ` George B.
2010-04-16 4:00 ` George B.
2010-04-16 4:53 ` Eric Dumazet [this message]
2010-04-16 7:28 ` George B.
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=1271393633.16881.3606.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=georgeb@gmail.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