From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: netdev <netdev@oss.sgi.com>, "David S. Miller" <davem@davemloft.net>
Subject: Re: patch: Action repeat
Date: Sun, 01 May 2005 02:06:12 +0200 [thread overview]
Message-ID: <42741D74.2070400@trash.net> (raw)
In-Reply-To: <1114890709.8929.147.camel@localhost.localdomain>
jamal wrote:
> You mean not passing it back via skbs but through something else?
> What do you have in mind?
> It does sound distasteful for either changing the ->act()
> parametrization just so we can have a classid passed back or provide a
> spot for it in struct tc_action since only some actions will need to
> change it.
I meant changing ->act() to have the same prototype as tcf_act_exec()
itself:
- int (*act)(struct sk_buff **, struct tc_action *);
+ int (*act)(struct sk_buff **, struct tc_action *, struct
tcf_result *);
> I see the issue with classid leaking - perhaps specific actions could
> reset it when they steal packets? We should also reset it if the packet
> is stolen.
Since its already reset after actions are executed, we only need to
additionally reset it for packets that take a different path.
At the moment I think this only happens with mirred.
Regards
Patrick
next prev parent reply other threads:[~2005-05-01 0:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 16:50 patch: Action repeat jamal
2005-04-30 17:06 ` Patrick McHardy
2005-04-30 17:08 ` Patrick McHardy
2005-04-30 17:27 ` jamal
2005-04-30 18:13 ` Patrick McHardy
2005-04-30 19:51 ` jamal
2005-04-30 20:08 ` Thomas Graf
2005-04-30 20:50 ` jamal
2005-04-30 21:55 ` Thomas Graf
2005-04-30 22:34 ` jamal
2005-04-30 23:58 ` Thomas Graf
2005-05-02 12:10 ` jamal
2005-05-02 15:06 ` Thomas Graf
2005-05-04 11:46 ` jamal
2005-05-04 12:15 ` Patrick McHardy
2005-05-04 12:31 ` Thomas Graf
2005-05-04 12:59 ` jamal
2005-05-04 13:28 ` Thomas Graf
2005-05-04 13:33 ` Thomas Graf
2005-05-04 13:33 ` jamal
2005-05-04 13:48 ` Thomas Graf
2005-05-04 13:53 ` jamal
2005-05-04 14:05 ` Thomas Graf
2005-05-04 14:23 ` jamal
2005-05-04 14:53 ` Thomas Graf
2005-05-05 13:06 ` jamal
2005-05-01 0:08 ` Patrick McHardy
2005-05-01 0:06 ` Patrick McHardy [this message]
2005-05-03 23:28 ` David S. Miller
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=42741D74.2070400@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).