From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davidm@hpl.hp.com
Cc: akpm@zip.com.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: proc_misc.c bug
Date: 10 Apr 2003 22:44:17 +0100 [thread overview]
Message-ID: <1050011057.12930.134.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200304102202.h3AM2YH3021747@napali.hpl.hp.com>
On Thu, 2003-04-10 at 23:02, David Mosberger wrote:
> The workaround below is to allocate 4KB per 8 CPUs. Not really a
> solution, but the fundamental problem is that /proc/interrupts
> shouldn't use a fixed buffer size in the first place. I suppose
> another solution would be to use vmalloc() instead. It all feels like
> bandaids though.
How about switching to Al's seqfile interface ?
next prev parent reply other threads:[~2003-04-10 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 22:02 David Mosberger
2003-04-10 21:44 ` Alan Cox [this message]
2003-04-10 22:49 ` Randy.Dunlap
2003-04-11 5:01 ` Randy.Dunlap
2003-04-11 5:28 ` Andrew Morton
2003-04-11 5:41 ` David Mosberger
2003-04-11 5:46 ` Zwane Mwaikambo
2003-04-11 17:29 ` Randy.Dunlap
2003-04-11 18:32 ` David Mosberger
2003-04-10 22:53 ` Andrew Morton
2003-04-11 0:27 ` David Mosberger
2003-04-10 22:18 ` Andrew Morton
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=1050011057.12930.134.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@zip.com.au \
--cc=davidm@hpl.hp.com \
--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
all inboxes | Powered by JetHome®