On Mon, 2010-02-01 at 12:25 +0200, Alexey Dobriyan wrote:

On Mon, Feb 1, 2010 at 12:12 PM, Eric Dumazet [off-list ref] wrote:

quoted

Le lundi 01 février 2010 à 11:36 +0200, Alexey Dobriyan a écrit :

quoted

On Mon, Feb 1, 2010 at 11:32 AM, Jon Masters [off-list ref] wrote:

quoted

I hacked up a per-namespace version of hashtables (this needs doing
anyway, since the global stuff is just waiting to break)

Which ones? Conntrack hashtables are per-netns.

It seems they are, but this is not a complete work :

That's my point.

They are per-netns.

It's not "complete", because right now there is no point in doing more.
nf_conntrack_max was rejected given the absense of per-netns kernel
memory consumption limiting.

quoted

1) Global settings (shared by all netns)

Only hashtable size which is module parameter and
there is no generic way to limit kernel memory (like beancounters).

And can be changed at any time you like (also an exported symbol) such
that existing hashtable indexing will fail and corrupt memory. There is
clearly a need for each of these hashtables to have its own metadata.

Jon.