From: john slee <indigoid@higherplane.net>
To: linux-kernel@vger.kernel.org
Cc: Rik van Riel <riel@conectiva.com.br>
Subject: Re: system call for process information?
Date: Wed, 14 Mar 2001 12:59:31 +1100 [thread overview]
Message-ID: <20010314125931.H918@higherplane.net> (raw)
In-Reply-To: <200103132105.f2DL5D8411265@saturn.cs.uml.edu> <Pine.LNX.4.21.0103131951590.2056-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0103131951590.2056-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Tue, Mar 13, 2001 at 07:52:41PM -0300
On Tue, Mar 13, 2001 at 07:52:41PM -0300, Rik van Riel wrote:
> On Tue, 13 Mar 2001, Albert D. Cahalan wrote:
>
> > Bloat removal: being able to run without /proc mounted.
> >
> > We don't have "kernel speed". We have kernel-mode screwing around
> > with text formatting.
>
> Sounds like you might want to maintain an external patch
> for the embedded folks...
or perhaps a patch to remove the non-procfs stuff from proc - leaving
just /proc/[0-9]+ and /proc/self...
that way top/ps/ still mostly work without patches and you dont have all
the other stuff that you don't need (perhaps make a separate kernfs?).
i *am* aware of the previous flamewars over this :-) but it does appear
to me a more generally useful compromise in the anti-bloat case.
j. (who likes proc as it is now)
next prev parent reply other threads:[~2001-03-14 1:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 17:08 system call for process information? Guennadi Liakhovetski
2001-03-12 18:27 ` Alexander Viro
2001-03-12 21:21 ` Guennadi Liakhovetski
2001-03-13 2:56 ` Nathan Paul Simons
2001-03-13 3:20 ` Alexander Viro
2001-03-13 9:55 ` Guennadi Liakhovetski
2001-03-13 21:05 ` Albert D. Cahalan
2001-03-13 22:02 ` Nathan Paul Simons
2001-03-13 22:50 ` Albert D. Cahalan
2001-03-13 22:52 ` Rik van Riel
2001-03-14 1:53 ` Martin Dalecki
2001-03-14 2:28 ` Rik van Riel
2001-03-14 8:24 ` george anzinger
2001-03-14 19:19 ` Rik van Riel
2001-03-14 16:27 ` george anzinger
2001-03-15 12:24 ` changing mm->mmap_sem (was: Re: system call for process information?) Rik van Riel
2001-03-15 12:24 ` Rik van Riel
2001-03-16 9:49 ` Stephen C. Tweedie
2001-03-16 9:49 ` Stephen C. Tweedie
2001-03-16 11:50 ` Rik van Riel
2001-03-16 11:50 ` Rik van Riel
2001-03-16 12:53 ` Stephen C. Tweedie
2001-03-16 12:53 ` Stephen C. Tweedie
2001-03-18 7:23 ` Rik van Riel
2001-03-18 7:23 ` Rik van Riel
2001-03-18 9:56 ` Mike Galbraith
2001-03-18 9:56 ` Mike Galbraith
2001-03-18 10:46 ` Rik van Riel
2001-03-18 10:46 ` Rik van Riel
2001-03-18 12:33 ` Mike Galbraith
2001-03-18 12:33 ` Mike Galbraith
2001-03-14 1:59 ` john slee [this message]
2001-03-14 19:53 ` system call for process information? Szabolcs Szakacsits
2001-03-14 19:55 ` Alexander Viro
2001-03-14 20:23 ` Szabolcs Szakacsits
2001-03-14 20:21 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 12:17 Rajiv Majumdar
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=20010314125931.H918@higherplane.net \
--to=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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.