From: Fan Du <fan.du@windriver.com>
To: <steffen.klassert@secunet.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: [PATCHv4 net-next 0/2] Make flow cache name space aware
Date: Sat, 18 Jan 2014 09:55:26 +0800 [thread overview]
Message-ID: <1390010128-15835-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.
v2:
- Pick up newly created file include/net/flowcache.h missed in v1.
v3:
- I made a mistake by spreading one unified patch into different
patches, which break bisect operation. So forge into one piece
patches advised by Cong and Sabrina.
v4:
- Fix selinux xfrm compiling issue.
Fan Du (2):
flowcache: Make flow cache name space aware
flowcache: Bring net/core/flow.c under IPsec maintain scope
MAINTAINERS | 1 +
include/net/flow.h | 5 +-
include/net/flowcache.h | 25 ++++++++
include/net/netns/xfrm.h | 11 ++++
net/core/flow.c | 127 ++++++++++++++++++---------------------
net/xfrm/xfrm_policy.c | 7 ++-
security/selinux/include/xfrm.h | 5 +-
7 files changed, 104 insertions(+), 77 deletions(-)
create mode 100644 include/net/flowcache.h
--
1.7.9.5
next reply other threads:[~2014-01-18 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 1:55 Fan Du [this message]
2014-01-18 1:55 ` [PATCHv4 net-next 1/2] flowcache: Make flow cache name space aware Fan Du
2014-01-18 1:55 ` [PATCHv4 net-next 2/2] 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=1390010128-15835-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