From: Anton Blanchard <anton@samba.org>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [CFT][PATCH] large /proc/mounts and friends
Date: Tue, 16 Oct 2001 14:05:39 +1000 [thread overview]
Message-ID: <20011016140539.A2426@krispykreme> (raw)
In-Reply-To: <Pine.GSO.4.21.0110152050010.11608-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0110152050010.11608-100000@weyl.math.psu.edu>
Hi,
> Folks, patch below adds a new way to handle large files on procfs.
> I've done that for /proc/mounts and /proc/ksyms, but the same trick can
> be pulled for anything else. The basic idea: if file consists of records
> generated by some sequence of objects, we can just describe an iterator and
> use precanned functions to turn it into a file. That (and helpers for
> formatting) is done in fs/seq_file.c and include/linux/seq_file.h.
Ahh good I was just going to fix /proc/stat and /proc/interrupts; given
enough interrupts and cpus they both overflow 1 page and cause random
memory corruption.
Anton
prev parent reply other threads:[~2001-10-16 4:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 1:10 [CFT][PATCH] large /proc/mounts and friends Alexander Viro
2001-10-16 3:01 ` Linus Torvalds
2001-10-16 3:45 ` Alexander Viro
2001-10-16 4:01 ` Linus Torvalds
2001-10-16 4:08 ` Alexander Viro
2001-10-16 9:58 ` Chris Wedgwood
2001-10-16 3:52 ` Linus Torvalds
2001-10-16 4:03 ` Alexander Viro
2001-10-16 4:29 ` Linus Torvalds
2001-10-16 4:41 ` Linus Torvalds
2001-10-16 5:16 ` Keith Owens
2001-10-17 2:09 ` Alexander Viro
2001-10-16 4:43 ` Alexander Viro
2001-10-16 4:05 ` Anton Blanchard [this message]
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=20011016140539.A2426@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.