All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: SV: [LARTC] Loadbalancing on multiple eth rtl8139
Date: Mon, 16 Oct 2000 14:10:17 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216788@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216786@msgid-missing>

<PRE>On Mon, Oct 16, 2000 at 01:44:50PM +0200, Daniel Bergqvist wrote:
&gt;<i> Hi!
</I>&gt;<i> 
</I>&gt;<i> The devices eth1 and eth3 MUST be active. Remove &quot;ip link set down eth1&quot; and
</I>&gt;<i> &quot;ip link set down eth3&quot;. You might get problems with &quot;TCP packet reordering&quot;
</I>&gt;<i> resulting in lower bandwidth but I'm currently working with a patch to the
</I>&gt;<i> sch_teql driver. I will post it to the list if/when I get it to work.
</I>
Read the archive of <A HREF="mailto:netdev@oss.sgi.com">netdev@oss.sgi.com</A>, I discussed it with Alexey and Jamal
there and they had some reservations about the idea. What might work is set
up the bundled device, and run a tcp/ip tunnel over it, like 'vtund'. This
lets the Linux TCP/IP stack reorder packets. Linux is not disturbed by
simple reordering problems, and thus solves your problems.

The only remaining problem is that tunneling over tcp/ip has some problems
of its own.

Regards,

bert hubert

-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>

  reply	other threads:[~2000-10-16 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-16 11:44 SV: [LARTC] Loadbalancing on multiple eth rtl8139 Daniel
2000-10-16 14:10 ` bert [this message]
2000-10-17 15:42 ` Miro
2000-10-17 18:55 ` bert

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=marc-lartc-98373938216788@msgid-missing \
    --to=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.