From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6 5/5]: act_api: mark some functions static/remove unused function
Date: Thu, 04 Nov 2004 17:24:24 +0100 [thread overview]
Message-ID: <418A57B8.9040205@trash.net> (raw)
In-Reply-To: <1099583639.1081.30.camel@jzny.localdomain>
jamal wrote:
>On Thu, 2004-11-04 at 10:28, Patrick McHardy wrote:
>
>>Ok, here is the same patch without removing tc_lookup_action_id.
>>It is instead surrounded by #if 0.
>>
>
>
>Why is this function bothering you? ;->
>Why do you need to put the #if 0?
>
Because the compiler will warn about an unused static function.
>>- move the functions from include/net/pkt_act.h to act_generic.c
>>
>
>Some of the larger ones make sense to move. Whats the main reason for
>moving them?
>
I was talking about the larger ones. There are multiple
large inline functions that are used by all(?) actions.
>These two make sense. I need help eyeballing the iptables stuff.
>I commented out some of the refcount attempts; also i think quiet a
>few targets are not friendly in getting accessed by anything other than
>iptables; I was going at some point fix them and send you guys patches.
>Maybe you can help me in this area as well.
>
>
I can't think of a reason why targets would mind beeing used by ipt,
but I'll look out for problems.
>>Is there already userspace-code for anything besides gact ?
>>I would like to test my changes.
>>
>>
>>
>
>Stephen is probably stalled somewhere because he hasnt been sucking in
>my updates to iproute2.
>I have the latest and greatest on my test machine at home. But here
>are tc updates for ipt and mirred that i could find on my laptop.
>
>
Thanks.
>The ipt patch needs iptables libraries and may not work with latest
>iptables (although the one at home will surely work). The problem is
>some of the iptables functions were updated. It would be nice if i didnt
>have to maintain my own variants in user space.
>
>
I can't see a way to avoid this currently.
Regards
Patrick
next prev parent reply other threads:[~2004-11-04 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4189CB70.3060703@trash.net>
2004-11-04 13:56 ` [PATCH 2.6 5/5]: act_api: mark some functions static/remove unused function jamal
2004-11-04 15:28 ` Patrick McHardy
2004-11-04 15:53 ` jamal
2004-11-04 16:24 ` Patrick McHardy [this message]
2004-11-04 16:31 ` jamal
2004-11-04 16:34 ` Jamal Hadi Salim
2004-11-04 16:50 ` Patrick McHardy
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=418A57B8.9040205@trash.net \
--to=kaber@trash.net \
--cc=davem@redhat.com \
--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).