netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arturo Borrero Gonzalez <arturo@netfilter.org>
To: Manoj Basapathi <manojbm@codeaurora.org>,
	netfilter-devel@vger.kernel.org
Cc: subashab@quicinc.com, sharathv@qti.qualcomm.com,
	ssaha@qti.qualcomm.com, vidulak@qti.qualcomm.com,
	bryanh@quicinc.com, jovanar@qti.qualcomm.com,
	manojbm@qti.qualcomm.com
Subject: Re: [PATCH] netfilter: xtables: Add snapshot of hardidletimer target
Date: Tue, 12 Nov 2019 12:02:36 +0100	[thread overview]
Message-ID: <4fac187b-3a13-c762-a619-d09585ecd718@netfilter.org> (raw)
In-Reply-To: <20191111065617.GA29048@manojbm-linux.ap.qualcomm.com>

On 11/11/19 7:56 AM, Manoj Basapathi wrote:
> This is a snapshot of hardifletimer netfilter target as of msm-4.4
> commit 469a150b7426 ("netfilter: xtables: hardidletimer target implementation")
> 
> This patch implements a hardidletimer Xtables target that can be
> used to identify when interfaces have been idle for a certain period
> of time.
> 
> Timers are identified by labels and are created when a rule is set
> with a new label. The rules also take a timeout value (in seconds) as
> an option. If more than one rule uses the same timer label, the timer
> will be restarted whenever any of the rules get a hit.
> 
> One entry for each timer is created in sysfs. This attribute contains
> the timer remaining for the timer to expire. The attributes are
> located under the xt_idletimer class:
> 
> /sys/class/xt_hardidletimer/timers/<label>
> 
> When the timer expires, the target module sends a sysfs notification
> to the userspace, which can then decide what to do (eg. disconnect to
> save power)
> 
> Compared to xt_IDLETIMER, xt_HARDIDLETIMER can send notifications when
> CPU is in suspend too, to notify the timer expiry.
> 
> Change-Id: Ib2e05af7267f3c86d1967f149f7e7e782c59807e
> Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
> Signed-off-by: Manoj Basapathi <manojbm@codeaurora.org>
> ---
>  .../uapi/linux/netfilter/xt_HARDIDLETIMER.h   |  51 +++
>  net/netfilter/Kconfig                         |  14 +
>  net/netfilter/Makefile                        |   1 +
>  net/netfilter/xt_HARDIDLETIMER.c              | 381 ++++++++++++++++++
>  net/netfilter/xt_IDLETIMER.c                  |   2 +
>  5 files changed, 449 insertions(+)
>  create mode 100644 include/uapi/linux/netfilter/xt_HARDIDLETIMER.h
>  create mode 100644 net/netfilter/xt_HARDIDLETIMER.c

I have nothing to comment on the patch itself.

But I wonder what would it take to implement this in the nf_tables framework.

  reply	other threads:[~2019-11-12 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  6:56 [PATCH] netfilter: xtables: Add snapshot of hardidletimer target Manoj Basapathi
2019-11-12 11:02 ` Arturo Borrero Gonzalez [this message]
2019-11-12 11:14 ` Florian Westphal
2019-11-12 18:44   ` manojbm
2019-11-12 18:53   ` manojbm

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=4fac187b-3a13-c762-a619-d09585ecd718@netfilter.org \
    --to=arturo@netfilter.org \
    --cc=bryanh@quicinc.com \
    --cc=jovanar@qti.qualcomm.com \
    --cc=manojbm@codeaurora.org \
    --cc=manojbm@qti.qualcomm.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sharathv@qti.qualcomm.com \
    --cc=ssaha@qti.qualcomm.com \
    --cc=subashab@quicinc.com \
    --cc=vidulak@qti.qualcomm.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).