All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <cwang@twopensource.com>
To: Dmitry Sytchev <kbdfck@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Why do we prefer skb->priority to tc filters?
Date: Thu, 12 Mar 2015 10:08:29 -0700	[thread overview]
Message-ID: <CAHA+R7PrxZKaRsjUBxLaitNdZwute-0saOxj+hza8zCya-hT2Q@mail.gmail.com> (raw)
In-Reply-To: <CA+GmxbbGHXrZ6OrwPm0WBzk89iK94wyzJJAqbqw_XbVELvy9nQ@mail.gmail.com>

On Thu, Mar 12, 2015 at 12:53 AM, Dmitry Sytchev <kbdfck@gmail.com> wrote:
> Sorry for slight offtopic, but for some reason, recent netfilter SET
> changes, which allow setting queue number and priority via ipset
> skbinfo extension, don't work with multiple HTB on top of multiq or
> mq.

Can you show us your setup? `iptables -L` and `tc qd show dev ...`,
`tc class show dev ...` etc.


> At the same time, tc filters set on outbound iface with skbedit works
> fine both for prio and queue number.
> How can I find the difference in their behaviour to trace where queue
> number set by ipset match gets lost?

There are fewer places to set skb->queue_mapping than skb->priority.
Since you are using mq, you can watch the `tc -s -d class show dev ...`
output to see if your packets go to the desired queue.

      reply	other threads:[~2015-03-12 17:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 17:34 Why do we prefer skb->priority to tc filters? Cong Wang
2015-03-11 18:08 ` Cong Wang
2015-03-11 18:25   ` Eric Dumazet
2015-03-11 19:18     ` Cong Wang
2015-03-11 20:09       ` Eric Dumazet
2015-03-11 20:46         ` Cong Wang
2015-03-11 21:47           ` Eric Dumazet
2015-03-11 22:12             ` Cong Wang
2015-03-12  0:00               ` Eric Dumazet
2015-03-12 16:59                 ` Cong Wang
2015-03-12 17:25                   ` Cong Wang
2015-03-12  7:53             ` Dmitry Sytchev
2015-03-12 17:08               ` Cong Wang [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=CAHA+R7PrxZKaRsjUBxLaitNdZwute-0saOxj+hza8zCya-hT2Q@mail.gmail.com \
    --to=cwang@twopensource.com \
    --cc=kbdfck@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 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.