From: David Laight <David.Laight@ACULAB.COM>
To: 'Matthew Wilcox' <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Waiman Long <longman@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Kees Cook <keescook@chromium.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
"Miklos Szeredi" <miklos@szeredi.hu>,
Daniel Colascione <dancol@google.com>,
"Dave Chinner" <david@fromorbit.com>,
Randy Dunlap <rdunlap@infradead.org>,
"Marc Zyngier" <marc.zyngier@arm.com>
Subject: RE: [patch V2 1/2] genriq: Avoid summation loops for /proc/stat
Date: Wed, 13 Feb 2019 15:55:07 +0000 [thread overview]
Message-ID: <3460540b50784dca813a57ddbbd41656@AcuMS.aculab.com> (raw)
In-Reply-To: <20190209034117.GC21860@bombadil.infradead.org>
From: Matthew Wilcox
> Sent: 09 February 2019 03:41
>
> On Fri, Feb 08, 2019 at 03:21:51PM -0800, Andrew Morton wrote:
> > It sounds like it. A 10khz interrupt will overflow in 4 days...
>
> If you've got a 10kHz interrupt, you have a bigger problem. Anything
> happening 10,000 times a second is going to need interrupt mitigation
> to perform acceptably.
Not necessarily - you may want the immediate interrupt for each
received ethernet packet.
> More importantly, userspace can (and must) cope with wrapping. This isn't
> anything new from Thomas' patch. As long as userspace is polling more
> often than once a day, it's going to see a wrapped value before it wraps
> again, so it won't miss 4 billion interrupts.
If userspace is expected to detect wraps, making the sum 64bit is
pointless, confusing and stupid.
The code would have to mask off the high bits before determining
that the value has decreased and then adding in 2^32.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2019-02-13 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 13:48 [patch V2 0/2] genirq, proc: Speedup /proc/stat interrupt statistics Thomas Gleixner
2019-02-08 13:48 ` [patch V2 1/2] genriq: Avoid summation loops for /proc/stat Thomas Gleixner
2019-02-08 22:32 ` Andrew Morton
2019-02-08 22:46 ` Waiman Long
2019-02-08 23:21 ` Andrew Morton
2019-02-09 3:41 ` Matthew Wilcox
2019-02-13 15:55 ` David Laight [this message]
2019-02-08 13:48 ` [patch V2 2/2] proc/stat: Make the interrupt statistics more efficient Thomas Gleixner
2019-02-08 17:01 ` Alexey Dobriyan
2019-02-08 15:20 ` [patch V2 0/2] genirq, proc: Speedup /proc/stat interrupt statistics Waiman Long
2019-02-08 17:01 ` Davidlohr Bueso
2019-02-08 17:40 ` Marc Zyngier
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=3460540b50784dca813a57ddbbd41656@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dancol@google.com \
--cc=dave@stgolabs.net \
--cc=david@fromorbit.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=marc.zyngier@arm.com \
--cc=miklos@szeredi.hu \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.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 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).