From: David Miller <davem@davemloft.net>
To: cwang@twopensource.com
Cc: jhs@mojatatu.com, netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: Is sch_teql still useful?
Date: Sun, 01 Feb 2015 22:27:41 -0800 (PST) [thread overview]
Message-ID: <20150201.222741.1721645652546390344.davem@davemloft.net> (raw)
In-Reply-To: <CAHA+R7NDfn705P0OrgpMfx7nbsNcHh-cXrPVQezG9WtH1Ya3Yg@mail.gmail.com>
From: Cong Wang <cwang@twopensource.com>
Date: Fri, 30 Jan 2015 20:23:32 -0800
> Since we have bonding alb, is it still needed to have sch_teql since
> they do the same thing, load balancing over multiple interfaces? Also
> sch_teql mixes netdevice with qdisc, which somewhat breaks the
> abstraction?
>
> I don't dig the history so I could easily miss something here.
I can't comment as to it's usefulness, but I will note that we don't
have the option of removing it if you are thinking about doing so.
prev parent reply other threads:[~2015-02-02 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 4:23 Is sch_teql still useful? Cong Wang
2015-02-02 6: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=20150201.222741.1721645652546390344.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cwang@twopensource.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).