From: jamal <hadi@cyberus.ca>
To: mahatma@eu.by
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.23+] ingress classify to [nf]mark
Date: Sun, 13 Jan 2008 14:44:44 -0500 [thread overview]
Message-ID: <1200253484.4427.33.camel@localhost> (raw)
In-Reply-To: <4788FF45.702@bspu.unibel.by>
Hi,
Please CC me in your responses (the way i do when i respond to you),
that way my filters prioritize your email.
On Sat, 2008-12-01 at 15:56 -0200, Dzianis Kahanovich wrote:
> I in doubts only about "action continue".
> To "and/or" behaviour one of best usage are (example):
I dont think you should be touching the action part at all primarily
because actions can set the mark after classification.
The action code (not the default) should be the override. IOW, if i
specify a ipt mark of some value i would expect that value to be what
goes into the network stack and not the default value you want. Same if
i had a series of actions which override each others settings of mark.
When we have a metadata action, we can remove the setting of tcindex
in the action OK result case (for now it doesnt harm).
In other words, just set the #ifndef action to set both the tcindex and
mark to some policy;
> # set bit 2 of mark to 0 (mark&0xfd|0) and continue
> tc filter add ... prio 1 ... flowid fd:0 action continue
> # continue
> tc filter add ... prio 2 ...
>
> - in current ingress_enqueue() code IMHO "case TC_ACT_OK:" will not reached
> for action continue. I use old (mark=...) solution only by this.
>
> I think, "skb->mark = (skb->mark&(res.classid>>16))|TC_H_MIN(res.classid);"
> must be in the end of ingress_enqueue() before "return result". And not
> depended to "NET_CLS_ACT". But while not test it.
> Or this:
> ---
> #ifdef CONFIG_NET_SCH_INGRESS_TC2MARK
> #ifdef CONFIG_NET_CLS_ACT
> skb->mark = (skb->mark&(res.classid>>16))|TC_H_MIN(res.classid);
> #else
> skb->mark = res.classid;
> #endif
> #endif
Please refer to what i said above; if what i said still doesnt make
sense i can create (the simple) patch.
cheers,
jamal
next prev parent reply other threads:[~2008-01-13 19:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 19:05 [PATCH 2.6.23+] ingress classify to [nf]mark Dzianis Kahanovich
2008-01-10 17:29 ` Patrick McHardy
2008-01-11 17:37 ` Dzianis Kahanovich
2008-01-10 21:39 ` jamal
2008-01-11 17:24 ` Dzianis Kahanovich
2008-01-11 14:59 ` jamal
2008-01-11 20:42 ` Dzianis Kahanovich
2008-01-12 3:03 ` jamal
2008-01-12 17:56 ` Dzianis Kahanovich
2008-01-13 19:44 ` jamal [this message]
2008-01-14 15:40 ` Dzianis Kahanovich
2008-01-14 12:56 ` jamal
2008-01-14 22:20 ` Dzianis Kahanovich
2008-01-16 12:45 ` jamal
2008-01-23 0:14 ` Dzianis Kahanovich
2008-01-23 16:42 ` Dzianis Kahanovich
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=1200253484.4427.33.camel@localhost \
--to=hadi@cyberus.ca \
--cc=mahatma@eu.by \
--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).