From: "Denis V. Lunev" <den@openvz.org>
To: herbert@gondor.apana.org.au
Cc: devel@openvz.org, netdev@vger.kernel.org, davem@davemloft.net
Subject: [PATCH 1/4] net: Tag the network flow with the network namespace it is in (v2)
Date: Fri, 30 Nov 2007 19:07:29 +0300 [thread overview]
Message-ID: <20071130160729.GA10153@iris.sw.ru> (raw)
As well as marking flows this indirectly marks the ipv4 routing cache
as every routing entry contains a flow.
It is useful to add the network namespace into flows as frequently
the routing information for ingoing and outgoing network packets is
collected into a flow structure which is then used for several functions
as it sorts out what is going on.
Changes from v1:
- remove flow.h dependency from net_namespace.h
Signed-off-by: Denis V. Lunev <den@openvz.org>
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
---
include/net/flow.h | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/include/net/flow.h b/include/net/flow.h
index af59fa5..9590bbe 100644
--- a/include/net/flow.h
+++ b/include/net/flow.h
@@ -10,7 +10,9 @@
#include <linux/in6.h>
#include <asm/atomic.h>
+struct net;
struct flowi {
+ struct net *fl_net;
int oif;
int iif;
__u32 mark;
--
1.5.3.rc5
reply other threads:[~2007-11-30 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071130160729.GA10153@iris.sw.ru \
--to=den@openvz.org \
--cc=davem@davemloft.net \
--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).