From: Fan Du <fan.du@windriver.com>
To: <steffen.klassert@secunet.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/4] Make flow cache name space aware
Date: Mon, 13 Jan 2014 15:49:04 +0800 [thread overview]
Message-ID: <1389599348-5214-1-git-send-email-fan.du@windriver.com> (raw)
Hi,
This patch set aims to make flow cache operating in a per net style
when inserting flow cache entry or flush flow cache. The reason to
do so is not much compelling but reasonable, which is flushing flow
cache in original implementation has global effective, the collateral
damage is netns with only a few flow cache entries has gone.
So this patch make flow cache running in a per net scope. Operation
from different netns won't interfere with each other. And the flushing
operation is worthwhile for the netns which supposed to be.
Fan Du (4):
flowcache: Namespacify flowcache global parameters with xfrm
flowcache: Make flowcache entry inserting/flushing in per-net style
flowcache: fixup flow cache part in xfrm policy
flowcache: Bring net/core/flow.c under IPsec maintain scope
MAINTAINERS | 1 +
include/net/flow.h | 5 +-
include/net/netns/xfrm.h | 11 ++++
net/core/flow.c | 127 +++++++++++++++++++++-------------------------
net/xfrm/xfrm_policy.c | 7 +--
5 files changed, 76 insertions(+), 75 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-01-13 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 7:49 Fan Du [this message]
2014-01-13 7:49 ` [PATCH net-next 1/4] flowcache: Namespacify flowcache global parameters with xfrm Fan Du
2014-01-13 7:49 ` [PATCH net-next 2/4] flowcache: Make flowcache entry inserting/flushing in per-net style Fan Du
2014-01-13 7:49 ` [PATCH net-next 3/4] flowcache: Fixup flow cache part in xfrm policy Fan Du
2014-01-13 19:42 ` Cong Wang
2014-01-13 7:49 ` [PATCH net-next 4/4] flowcache: Bring net/core/flow.c under IPsec maintain scope Fan Du
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=1389599348-5214-1-git-send-email-fan.du@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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