From: Jiri Pirko <jiri@resnulli.us>
To: Robert McCabe <robert.mccabe@rockwellcollins.com>
Cc: netdev@vger.kernel.org, McCabe@rockwellcollins.com
Subject: Re: [PATCH 1/1] net sched: Added the TC_LINKLAYER_CUSTOM linklayer type
Date: Tue, 4 Jul 2017 17:40:23 +0200 [thread overview]
Message-ID: <20170704154023.GC1865@nanopsycho> (raw)
In-Reply-To: <20170704153450.GB1865@nanopsycho>
Tue, Jul 04, 2017 at 05:34:50PM CEST, jiri@resnulli.us wrote:
>Tue, Jul 04, 2017 at 04:49:24PM CEST, robert.mccabe@rockwellcollins.com wrote:
>>> You dump stab->data to user. How is this related to TC_LINKLAYER_CUSTOM
>>> and howcome this "is to support user-space modification of the qdisc
>>> stab" as your description says? I'm confused...
>>
>>I have a related patch for iproute2 where the "custom" link-layer is
>>used to allow
>>user modification of the qdisc stab. Dumping stab->data to the user
>>is used in the
>>iproute2 patch to show the current size translation table.
>
>Even so, the kernel patch you sent does not make any sense. Introduces
>TC_LINKLAYER_CUSTOM but does not use it.
Also, please make you email working. Says to me:
** Address not found **
Your message wasn't delivered to McCabe@rockwellcollins.com because the address couldn't be found. Check for typos or unnecessary spaces and try again.
This is annoying.
next prev parent reply other threads:[~2017-07-04 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 0:14 [PATCH 1/1] net sched: Added the TC_LINKLAYER_CUSTOM linklayer type McCabe, Robert J
2017-07-04 0:14 ` [PATCH 1/1] tc: custom qdisc pkt size translation table McCabe, Robert J
2017-07-04 5:48 ` [PATCH 1/1] net sched: Added the TC_LINKLAYER_CUSTOM linklayer type Jiri Pirko
2017-07-04 14:49 ` Robert McCabe
2017-07-04 15:34 ` Jiri Pirko
2017-07-04 15:40 ` Jiri Pirko [this message]
2017-07-04 17:12 ` Robert McCabe
2017-07-05 7:01 ` Jiri Pirko
2017-07-06 9:03 ` David Laight
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=20170704154023.GC1865@nanopsycho \
--to=jiri@resnulli.us \
--cc=McCabe@rockwellcollins.com \
--cc=netdev@vger.kernel.org \
--cc=robert.mccabe@rockwellcollins.com \
/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