All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: Problem using tc-sfq with tc-flow for arbitrary hashing
Date: Tue, 28 Mar 2017 22:07:56 +0000	[thread overview]
Message-ID: <fd3dc4e3-1c95-c2b2-d328-d45e746e3b08@gmail.com> (raw)
In-Reply-To: <18AC8370-6B1E-4A01-B5E4-BA637BA485C0@gmail.com>

Carmelo Cascone wrote:
> Hi all,
>
> I have a problem in configuring tc-sfq along with tc-flow. I would like to hash packets not using the UDP/TCP 5-tuple (default beahvior of tc-sfq), but simply the pair <ipsrc, ipdst>. I’m having hard time using tc-flow and finding help on the web, as such I decided to drop an email to this list.
>
> The commands and error I get are:
>
> $ tc qdisc add dev eth6 root handle 1: sfq
> $ tc filter add dev eth6 parent 1:0 protocol ip prio 1 flow hash keys src,dst perturb 30 divisor 1024
> RTNETLINK answers: Invalid argument
> We have an error talking to the kernel
>
> I’m issuing these commands on a Debian 9 with a kernel v4.9.16
> Please note that the tc filter command is the same used in the tc-sfq documentation.
>
> What am I doing wrong? What is the invalid argument?

Looking through many years old Qos folder I found a file with an example.

I don't know why it's not documented, but but adding handle 1 to the
filter command makes your example work for me, in the sense that it's
not rejected - didn't test further.

Historically I would have said putting sfq on root of an eth wouldn't
do much, but with BQLs maybe things have changed.



  reply	other threads:[~2017-03-28 22:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 20:48 Problem using tc-sfq with tc-flow for arbitrary hashing Carmelo Cascone
2017-03-28 22:07 ` Andy Furniss [this message]
2017-03-30 13:44 ` Carmelo Cascone
2017-03-31 14:12 ` Andy Furniss

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=fd3dc4e3-1c95-c2b2-d328-d45e746e3b08@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=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.