From: David Miller <davem@davemloft.net>
To: den@openvz.org
Cc: containers@lists.osdl.org, devel@openvz.org,
netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH 1/2 2.6.25] netns: struct net content re-work (v3)
Date: Tue, 11 Dec 2007 04:19:26 -0800 (PST) [thread overview]
Message-ID: <20071211.041926.127612929.davem@davemloft.net> (raw)
In-Reply-To: <20071211115507.GA9947@iris.sw.ru>
From: "Denis V. Lunev" <den@openvz.org>
Date: Tue, 11 Dec 2007 14:55:07 +0300
> Recently David Miller and Herbert Xu pointed out that struct net becomes
> overbloated and un-maintainable. There are two solutions:
> - provide a pointer to a network subsystem definition from struct net.
> This costs an additional dereferrence
> - place sub-system definition into the structure itself. This will speedup
> run-time access at the cost of recompilation time
>
> The second approach looks better for us. Other sub-systems will follow.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> Acked-by: Daniel Lezcano <dlezcano@fr.ibm.com>
Applied.
prev parent reply other threads:[~2007-12-11 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 11:55 [PATCH 1/2 2.6.25] netns: struct net content re-work (v3) Denis V. Lunev
2007-12-11 12:19 ` David Miller [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=20071211.041926.127612929.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=containers@lists.osdl.org \
--cc=den@openvz.org \
--cc=devel@openvz.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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).