From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Patrick McHardy <kaber@trash.net>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH nf-next-2.6] netfilter: add xt_cpu match
Date: Thu, 22 Jul 2010 18:24:14 +0200 [thread overview]
Message-ID: <1279815854.2467.112.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.LSU.2.01.1007221736150.12308@obet.zrqbmnf.qr>
Le jeudi 22 juillet 2010 à 17:39 +0200, Jan Engelhardt a écrit :
> Never say never. "long" already bit people in the past, and now we
> have that CONFIG_COMPAT stuff.
>
I know pretty well the "long" problem, I received one of the first alpha
machine ever built in the world (DEC 3000 AXP, with a fast 133 MHz
cpu ;) ), before I began to use Linux :)
> If invert is the only flag, perhaps it makes sense to use __u8
> for it.
>
Quite frankly it brings more problems than plain u32
- Possible security problems (padding bytes). Not applicable to
iptables.
- Some arches have slow byte/short accesses (21064 for example :) )
"int" is the natural type, fast on all arches.
- Given alignment requirements of iptables rules, using less than 32bits
here saves no ram.
But I dont care that much.
I even see compiler doesnt want to use a XOR instruction :
00000018 <cpu_mt>:
18: 55 push %ebp
19: 8b 42 04 mov 0x4(%edx),%eax
1c: 64 8b 15 00 00 00 00 mov %fs:0x0,%edx
23: 89 e5 mov %esp,%ebp
25: 5d pop %ebp
26: 39 10 cmp %edx,(%eax)
28: 0f 94 c2 sete %dl
2b: 0f b6 d2 movzbl %dl,%edx
2e: 3b 50 04 cmp 0x4(%eax),%edx
31: 0f 95 c0 setne %al
34: c3 ret
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-22 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 14:03 [PATCH nf-next-2.6] netfilter: add xt_cpu match Eric Dumazet
2010-07-22 14:19 ` Jan Engelhardt
2010-07-22 15:18 ` Eric Dumazet
2010-07-22 15:39 ` Jan Engelhardt
2010-07-22 16:24 ` Eric Dumazet [this message]
2010-07-23 11:00 ` Patrick McHardy
2010-07-23 13:43 ` [PATCH iptables] extension: " Eric Dumazet
2010-07-23 14:13 ` Patrick McHardy
2010-07-23 16:46 ` Jan Engelhardt
2010-07-23 17:30 ` Eric Dumazet
2010-07-23 17:53 ` Jan Engelhardt
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=1279815854.2467.112.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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