All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hagood <david.hagood@gmail.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Netfilter user mailing list <netfilter@vger.kernel.org>
Subject: Re: Usefulness of xt_recent's "last seen" and "oldest_pkt" on a tickless system
Date: Sun, 11 Jan 2015 17:24:11 -0600	[thread overview]
Message-ID: <54B3061B.5000503@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1501111925200.24030@nerf60.vanv.qr>

On 01/11/2015 12:49 PM, Jan Engelhardt wrote:
> The jifs/sec is set by CONFIG_HZ, for which a common kernel only
> offers the compile-time choices of 100, 250, 300, 1000, not 2150.
> If you find a value of 2150, you are probably looking at the wrong
> value, or have a heavily modified custom kernel.
Nope. Standard Ubuntu 14.04 low latency kernel. And the value is 
computed by looking at the btime field in /proc/timer_list (not 
/proc/stat - my bad). Moreover, I can tell by causing a packet to be 
logged at a known time in a xt_recent rule, looking at the last_seen 
field, and then computing the ratio of the known time expressed as 
seconds since boot, and in jiffies from the kernel.

>
> TTBONK, there is no reliable way for userspace to tell the value of
> CONFIG_HZ, so yes, _showing_ jiffies in /proc/net/xt_recent is
> useless - but at least you can compare the numbers against each other
> (not that that seems useful, either).
>

Agreed.

  reply	other threads:[~2015-01-11 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 10:23 Usefulness of xt_recent's "last seen" and "oldest_pkt" on a tickless system Jan Engelhardt
2015-01-11 15:52 ` David Hagood
2015-01-11 18:49   ` Jan Engelhardt
2015-01-11 23:24     ` David Hagood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-11  1:27 David Hagood

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=54B3061B.5000503@gmail.com \
    --to=david.hagood@gmail.com \
    --cc=jengelh@inai.de \
    --cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.