All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: Using Unix TC to shape high bandwidth traffic
Date: Thu, 06 Aug 2015 17:01:15 +0000	[thread overview]
Message-ID: <55C392DB.8010406@gmail.com> (raw)
In-Reply-To: <E9450EA5C62BD943A17ACD921A227DD2054A3EA2@MMXDC2642.hermes.si.socgen>

LAMBRUSCHI Yannick (EXT) wrote:
> Hello,
>
>
> Thanks for the post. We also played with mtu 1514 (and even greater)
> but did not change anything. I really think it comes from the jiffy
> limit but can't find another way..

Strangely I have now tested with your command and mtu 1514 and I can get
gig speed OK.

I was thinking possibly you could just omit the peak rate and mtu (which
seems to be another buffer size) and see if it was OK.

I don't know why I am not limited like you but -

I am using tcp netperf.

My mobo gig nic is dumb so doesn't offload. I guess a 10 gig nic will
offload, so unless you already turned it off with ethtool it's possible
the kernel is sending huge packets to the nic.

Maybe try far bigger mtu or not bother with peakrate/mtu - FWIW setting
1000mbit peakrate is still going to be faster than a gig nic can go as
there are overheads above what tc sees.

It could be kernel settings - you mention jiffies, tbf is ancient and I
don't know whether it was ever changed, or if kernel settings can change
things.

I don't know why I am not limited like you grepping hz from my config
looks like -

ph4[1080i25]$ grep -i hz /boot/config-4.2.0-rc4-g194a336
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ\x1000
# CONFIG_MACHZ_WDT is not set

  parent reply	other threads:[~2015-08-06 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 13:38 Using Unix TC to shape high bandwidth traffic LAMBRUSCHI Yannick (EXT)
2015-08-06 12:09 ` Andy Furniss
2015-08-06 14:08 ` LAMBRUSCHI Yannick (EXT)
2015-08-06 17:01 ` Andy Furniss [this message]
2015-08-07  8:30 ` LAMBRUSCHI Yannick (EXT)
2015-08-07  8:44 ` Dave Taht
2015-08-17  8:51 ` LAMBRUSCHI Yannick (EXT)
2015-09-01 15:19 ` Marco Gaiarin

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=55C392DB.8010406@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.