From: jbarnes@sgi.com (Jesse Barnes)
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] seq_file version of /proc/interrupts
Date: Thu, 13 Nov 2003 10:02:56 -0800 [thread overview]
Message-ID: <20031113180255.GA27893@sgi.com> (raw)
In-Reply-To: <20031113173626.12557.qmail@lwn.net>
On Thu, Nov 13, 2003 at 10:36:26AM -0700, Jonathan Corbet wrote:
> This version should scale to something over 300 processors, after which it
> will not be possible to fit even a single line of /proc/interrupts output
> into one page. At that point, if this output format is even remotely
> useful, some sort of iterator which tracks interrupt and CPU numbers will
> be needed.
I assume you're talking about overflowing a 4k page? If so, we might be
able to limp along with the small 300p limit for awhile on ia64 since
most people running large systems use at least a 16k page size.
Thanks,
Jesse
next prev parent reply other threads:[~2003-11-13 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 17:36 [PATCH] seq_file version of /proc/interrupts Jonathan Corbet
2003-11-13 18:02 ` Jesse Barnes [this message]
2003-11-13 19:35 ` viro
2003-11-13 21:39 ` Jonathan Corbet
2003-11-13 22:26 ` Erik Jacobson
2003-11-20 16:58 ` Erik Jacobson
2003-12-23 0:22 ` Anton Blanchard
2003-12-23 0:38 ` Jonathan Corbet
2003-12-23 0:49 ` Andrew Morton
2003-12-23 1:18 ` Mike Fedyk
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=20031113180255.GA27893@sgi.com \
--to=jbarnes@sgi.com \
--cc=corbet@lwn.net \
--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