From: Nathan Zimmer <nzimmer@sgi.com>
To: unlisted-recipients:; (no To-header on input)
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Nathan Zimmer <nzimmer@sgi.com>
Subject: [PATCH v5 0/2] timer_list: Fix /proc/timer_list failure on 4096 cpus
Date: Tue, 26 Mar 2013 19:56:28 -0500 [thread overview]
Message-ID: <1364345790-14577-1-git-send-email-nzimmer@sgi.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1303251651200.22263@ionos>
On systems with 4096 cores attemping to read /proc/timer_list
fails because we are trying to push all the data into a single
kmalloc buffer.
A better solution is to not us the single_open mechanism but to
provide our own seq_operations and treat each cpu as an
individual record.
The output should be identical to the previous version.
v2: Added comments on the iteration and other fixups pointed to by Andrew.
v3: Corrected the case where max_cpus != nr_cpu_ids by exiting early.
v5: Use seq_open_private and supply a proper iterator rather then a big mess.
Nathan Zimmer (2):
timer_list: split timer_list_show_tickdevices
timer_list: convert timer list to be a proper seq_file
kernel/time/timer_list.c | 104 +++++++++++++++++++++++++++++++++++++----------
1 file changed, 83 insertions(+), 21 deletions(-)
--
1.8.1.2
next parent reply other threads:[~2013-03-27 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.02.1303251651200.22263@ionos>
2013-03-27 0:56 ` Nathan Zimmer [this message]
2013-03-27 0:56 ` [PATCH 1/2] timer_list: split timer_list_show_tickdevices Nathan Zimmer
2013-04-17 19:57 ` [tip:timers/core] timer_list: Split timer_list_show_tickdevices tip-bot for Nathan Zimmer
2013-03-27 0:56 ` [PATCH 2/2] timer_list: convert timer list to be a proper seq_file Nathan Zimmer
2013-03-27 19:14 ` Andrew Morton
2013-03-27 20:05 ` Thomas Gleixner
2013-04-17 19:58 ` [tip:timers/core] timer_list: Convert " tip-bot for Nathan Zimmer
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=1364345790-14577-1-git-send-email-nzimmer@sgi.com \
--to=nzimmer@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome