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 09:52:58 -0600 [thread overview]
Message-ID: <54B29C5A.3010708@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1501111106300.616@nerf60.vanv.qr>
On 01/11/2015 04:23 AM, Jan Engelhardt wrote:
>
>> are just a count of the number of jiffies since boot. However, on a
>> tickless kernel, there is really no well defined number of jiffies per
>> second as far as I can tell
>
> You might want to have a look at
> static void tick_do_update_jiffies64(ktime_t now) in
> kernel/time/tick-sched.c ;-)
>
Thanks for the reply - at least now I know somebody is listening.
However, I looked over the function in question, and it does not seem to
address my points:
1) It's a kernel only function. I am concerned about access from user space.
2) By inspection, my machine is running a jiffies per second value that
varies between 2145 and 2150 jiffies per second (computed by reading the
jiffies value from /proc/stat and reading the time since boot in
seconds). There's simply no way to use a number with that much
variability to compute when a packet was received - there has to be some
way to know what the conversion was at the time the packet was logged,
not at the current time. (and according to the configuration for the
kernel, the nominal HZ value should be 1000, but full tickless mode is
enabled - so that value does not seem to be used.)
next prev parent reply other threads:[~2015-01-11 15:52 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 [this message]
2015-01-11 18:49 ` Jan Engelhardt
2015-01-11 23:24 ` David Hagood
-- 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=54B29C5A.3010708@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.