From: wenxu@ucloud.cn
To: pablo@netfilter.org, paulb@mellanox.com
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH nf-next 2/3] netfilter: nf_flow_table: add nf_conn_acct for HW flowtable offload
Date: Sat, 21 Mar 2020 19:29:17 +0800 [thread overview]
Message-ID: <1584790158-9752-3-git-send-email-wenxu@ucloud.cn> (raw)
In-Reply-To: <1584790158-9752-1-git-send-email-wenxu@ucloud.cn>
From: wenxu <wenxu@ucloud.cn>
Add nf_conn_acct counter for the hardware flowtable offload
Signed-off-by: wenxu <wenxu@ucloud.cn>
---
net/netfilter/nf_flow_table_offload.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/net/netfilter/nf_flow_table_offload.c b/net/netfilter/nf_flow_table_offload.c
index a68136a..5b02bdd 100644
--- a/net/netfilter/nf_flow_table_offload.c
+++ b/net/netfilter/nf_flow_table_offload.c
@@ -784,6 +784,14 @@ static void flow_offload_work_stats(struct flow_offload_work *offload)
lastused = max_t(u64, stats[0].lastused, stats[1].lastused);
offload->flow->timeout = max_t(u64, offload->flow->timeout,
lastused + NF_FLOW_TIMEOUT);
+ if (stats[0].pkts)
+ flow_offload_update_acct(offload->flow, stats[0].pkts,
+ stats[0].bytes,
+ FLOW_OFFLOAD_DIR_ORIGINAL);
+ if (stats[1].pkts)
+ flow_offload_update_acct(offload->flow, stats[1].pkts,
+ stats[1].bytes,
+ FLOW_OFFLOAD_DIR_REPLY);
}
static void flow_offload_work_handler(struct work_struct *work)
--
1.8.3.1
next prev parent reply other threads:[~2020-03-21 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 11:29 [PATCH nf-next 0/3] netfilter: nf_flow_table_offload: add nf_conn_acct for flowtable offload wenxu
2020-03-21 11:29 ` [PATCH nf-next 1/3] netfilter: nf_flow_table: add nf_conn_acct for SW " wenxu
2020-03-21 11:29 ` wenxu [this message]
2020-03-21 11:29 ` [PATCH nf-next 3/3] net/sched: act_ct: add nf_conn_acct for SW act_ct " wenxu
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=1584790158-9752-3-git-send-email-wenxu@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=paulb@mellanox.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;
as well as URLs for NNTP newsgroup(s).