netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <cwang@twopensource.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	netdev <netdev@vger.kernel.org>,
	"Jamal Hadi Salim" <jhs@mojatatu.com>
Subject: Re: ingress policying for realtime protocol
Date: Wed, 20 May 2015 18:47:16 -0700	[thread overview]
Message-ID: <CAHA+R7OJ8WUtPg7zah17DgkNFtcJznjnT0ys-qYN2c_Trm6S3A@mail.gmail.com> (raw)
In-Reply-To: <1432168240.4060.63.camel@edumazet-glaptop2.roam.corp.google.com>

On Wed, May 20, 2015 at 5:30 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2015-05-20 at 16:46 -0700, Cong Wang wrote:
>
>> There is very little to do on ingress side since there is no queue at all,
>> not to mention priority, you could try ifb to see if it fits your need.
>
> Note that if the need is to police traffic, ifb is not really needed :
>

You really need to read Uwe's email before reply,
he mentioned prio qdisc:

"I wonder
what's missing to get ingress policying more versatile to allow for
example a prio qdisc or if there is some conceptual problem that I don't
see."

  reply	other threads:[~2015-05-21  1:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 21:11 ingress policying for realtime protocol Uwe Kleine-König
2015-05-20 23:46 ` Cong Wang
2015-05-21  0:30   ` Eric Dumazet
2015-05-21  1:47     ` Cong Wang [this message]
2015-05-21  1:53       ` Eric Dumazet
2015-05-21  1:59         ` Cong Wang
2015-05-21  2:32           ` Eric Dumazet
2015-05-21  7:07     ` Uwe Kleine-König
2015-05-21 13:36       ` Jamal Hadi Salim
2015-05-21 18:58         ` Uwe Kleine-König
2015-05-22 14:00           ` Jamal Hadi Salim
2015-05-21 14:04       ` Eric Dumazet

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=CAHA+R7OJ8WUtPg7zah17DgkNFtcJznjnT0ys-qYN2c_Trm6S3A@mail.gmail.com \
    --to=cwang@twopensource.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).