From: Patrick McHardy <kaber@trash.net>
To: adobriyan@gmail.com
Cc: containers@lists.linux-foundation.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 11/38] netns ct: per-netns unconfirmed hash
Date: Thu, 04 Sep 2008 18:46:00 +0200 [thread overview]
Message-ID: <48C010C8.9060808@trash.net> (raw)
In-Reply-To: <20080821224030.GB31601@x200.localdomain>
adobriyan@gmail.com wrote:
> What is unconfirmed connection in one netns can very well be confirmed
> in another.
>
> @@ -10,5 +11,6 @@ struct netns_ct {
> unsigned int expect_count;
> struct hlist_head *expect_hash;
> int expect_vmalloc;
> + struct hlist_head unconfirmed;
> };
You could lay this out a bit better to avoid holes and move
the members only used rarely (like *_vmalloc) to the end.
prev parent reply other threads:[~2008-09-04 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080821220059.GK31136@x200.localdomain>
2008-08-21 22:40 ` [PATCH 11/38] netns ct: per-netns unconfirmed hash adobriyan
2008-09-04 16:46 ` Patrick McHardy [this message]
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=48C010C8.9060808@trash.net \
--to=kaber@trash.net \
--cc=adobriyan@gmail.com \
--cc=containers@lists.linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).