netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: Dmitrii Shcherbakov <fw.dmitrii@yandex.com>,
	netdev@vger.kernel.org,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH][iproute2] tc/q_htb.c: Fix the MPU value output in 'tc -d class show dev <device_name> ' command
Date: Wed, 16 Dec 2015 17:04:00 +0100	[thread overview]
Message-ID: <20151216160400.GJ6555@orbit.nwl.cc> (raw)
In-Reply-To: <20151216161558.265296c7@redhat.com>

On Wed, Dec 16, 2015 at 04:15:58PM +0100, Jesper Dangaard Brouer wrote:
> When trying to understand this code, keep in mind that we are trying
> to keep backward compatible with older kernels.  Thus, this printing
> might be have been left here to keep compat with older kernels, but I
> think we can remove it now.

For a given kernel which still uses the upper eight bits of 'mpu' as
overhead value, iproute2 has become incompatible since commit
bccd014b866da ("Overhead calculation is now done in the kernel.") as
that eliminated the encoding while setting. So in order to stay
compatible, it should have left it in place while assigning to
opt.*.overhead in addition to that. Or the other way round, do the same
change to the output path as well.

So from a compatibility point of view, things are incompatible anyway.
Nobody complained, so I'd assume there are no users requiring this
(anymore). In fact, I couldn't even find the related change from using
'mpu>>8' to 'overhead' on kernel side.

Dmitrii, did iproute2 without your change even print the overhead as set
by you before? Looking at the code, I'd assume not.

Cheers, Phil

  reply	other threads:[~2015-12-16 16:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 11:09 [PATCH][iproute2] tc/q_htb.c: Fix the MPU value output in 'tc -d class show dev <device_name> ' command Dmitrii Shcherbakov
2015-12-16 15:15 ` Jesper Dangaard Brouer
2015-12-16 16:04   ` Phil Sutter [this message]
2015-12-16 20:56     ` Dmitrii Shcherbakov
2015-12-18 16:39     ` Dmitrii Shcherbakov
2015-12-18 16:55       ` Phil Sutter
2015-12-18 21:45         ` Dmitrii Shcherbakov
2015-12-22  5:45           ` Stephen Hemminger
2015-12-17  9:27   ` Dmitrii Shcherbakov
2015-12-17  9:45     ` Dmitrii Shcherbakov
2015-12-17 13:11       ` Phil Sutter

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=20151216160400.GJ6555@orbit.nwl.cc \
    --to=phil@nwl.cc \
    --cc=brouer@redhat.com \
    --cc=fw.dmitrii@yandex.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).