From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: rusty@rustcorp.com.au, netfilter-devel@lists.netfilter.org,
pablo@netfilter.org, kadlec@blackhole.kfki.hu
Subject: Re: [RFC][PATCH 0/7]: ct_extend
Date: Thu, 10 May 2007 14:34:00 +0200 [thread overview]
Message-ID: <46431138.2080805@trash.net> (raw)
In-Reply-To: <200705091105.l49B5DTu023689@toshiba.co.jp>
Yasuyuki KOZAKAI wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Tue, 08 May 2007 11:46:40 +0200
>
>>This will add quite some overhead since at least nfct_help is looked at
>>for every packet (we might avoid this using a status flag though).
>>I'm guessing the locks are needed to protect against concurrent
>>reallocations. Maybe we can avoid this by adding the limitation that
>>only unconfirmed entries may add new extensions?
>
>
> It sounds good to avoid competition of 2 packet processing. I think
> that the remain is nfctnetlink. It can assign helper to a confirmed
> conntrack. Do you think that it's enough to assume that it disables bh ?
No, that would only help for the CPU its running on. But so far
we only allow to change helpers, not assign completely new ones,
so no reallocation is needed. I'm wondering if this behaviour
is correct though ..
next prev parent reply other threads:[~2007-05-10 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 12:00 [RFC][PATCH 0/7]: ct_extend Yasuyuki KOZAKAI
2007-05-08 9:46 ` Patrick McHardy
2007-05-09 11:05 ` Yasuyuki KOZAKAI
[not found] ` <200705091105.l49B5DTu023689@toshiba.co.jp>
2007-05-10 12:34 ` Patrick McHardy [this message]
2007-05-11 1:51 ` Yasuyuki KOZAKAI
2007-05-30 23:43 ` Mohammad Mohsenzadeh
2007-05-31 4:38 ` Patrick McHardy
2007-05-31 9:02 ` Yasuyuki KOZAKAI
[not found] ` <200705310902.l4V9212d010654@toshiba.co.jp>
2007-06-01 15:33 ` Patrick McHardy
2007-06-04 0:45 ` Yasuyuki KOZAKAI
[not found] ` <200706040045.l540jnhh008964@toshiba.co.jp>
2007-06-04 11:58 ` 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=46431138.2080805@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.org \
--cc=rusty@rustcorp.com.au \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.