From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Daniel Borkmann <daniel@iogearbox.net>, Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com
Subject: Re: [PATCH -next 0/5] replace skb tc_verd member with 3 dedicated bit flags
Date: Tue, 05 May 2015 09:22:38 -0400 [thread overview]
Message-ID: <5548C41E.5020308@mojatatu.com> (raw)
In-Reply-To: <5548B984.5000900@iogearbox.net>
On 05/05/15 08:37, Daniel Borkmann wrote:
> On 05/05/2015 01:58 PM, Jamal Hadi Salim wrote:
>
> ... I quite frankly find the transformation after Florian's series
> *MUCH*, *MUCH* more intuitive, also given that we use such kind of
> bit flags already extensively everywhere in else the stack.
>
But he has to go around and change all occurrences where the macros are
invoked.
In some cases nothing has changed; in such a case the macros are useful
for hiding what goes on.
In any case - this is not as a big issue.
> What's more is that we reduce skbuff usage by 13-12 bits (given the
> follow up fix with AT_STACK is addressed).
>
Thats an orthogonal issue. Those bits were useful a few years ago,
and the use cases didnt pan out. So iam not against getting recycling.
> I think that can be done as a follow-up *after* the series.
Sure. Would of course be better to do it in this series if changes
are going to be made.
> Given
> it's uapi (which probably never should have been?) it's a different
> question on its own.
>
> Looking at git log include/uapi/linux/pkt_cls.h, it slipped in via
> David Howells uapi script ...
>
> commit 607ca46e97a1b6594b29647d98a32d545c24bdff
> Author: David Howells <dhowells@redhat.com>
> Date: Sat Oct 13 10:46:48 2012 +0100
>
Should never have been in uapi.
I dont think i saw that submission you pointed to.
But the problem may have existed before that patch.
cheers,
jamal
next prev parent reply other threads:[~2015-05-05 13:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 18:48 [PATCH -next 0/5] replace skb tc_verd member with 3 dedicated bit flags Florian Westphal
2015-05-04 18:48 ` [PATCH -next 1/5] net: sched: replace NCLS macro with tc_nocls bit flag Florian Westphal
2015-05-05 10:38 ` Daniel Borkmann
2015-05-05 23:15 ` David Miller
2015-05-04 18:48 ` [PATCH -next 2/5] net: sched: use counter to break reclassify loops Florian Westphal
2015-05-05 10:47 ` Daniel Borkmann
2015-05-04 18:48 ` [PATCH -next 3/5] net: sched: remove FROM INGRESS/EGRESS Florian Westphal
2015-05-05 10:51 ` Daniel Borkmann
2015-05-04 18:48 ` [PATCH -next 4/5] net: sched: remove AT INGRESS/EGRESS Florian Westphal
2015-05-05 11:06 ` Daniel Borkmann
2015-05-05 11:11 ` Florian Westphal
2015-05-04 18:48 ` [PATCH -next 5/5] skbuff: remove tc_verd member Florian Westphal
2015-05-05 11:09 ` Daniel Borkmann
2015-05-05 11:39 ` [PATCH -next 0/5] replace skb tc_verd member with 3 dedicated bit flags Jamal Hadi Salim
2015-05-05 11:47 ` Florian Westphal
2015-05-05 11:58 ` Jamal Hadi Salim
2015-05-05 12:37 ` Daniel Borkmann
2015-05-05 13:22 ` Jamal Hadi Salim [this message]
2015-05-05 13:06 ` Florian Westphal
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=5548C41E.5020308@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=fw@strlen.de \
--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 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).