From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: "Rus V. Brushkoff" <rus@domain.hid>, xenomai@xenomai.org
Subject: Re: [Xenomai-help] Error: cat: /proc/xenomai/stat: Cannot allocate memory
Date: Fri, 02 Feb 2007 15:42:54 +0100 [thread overview]
Message-ID: <45C34DEE.2020101@domain.hid> (raw)
In-Reply-To: <1170426719.4981.66.camel@domain.hid>
[-- Attachment #1.1: Type: text/plain, Size: 1029 bytes --]
Philippe Gerum wrote:
> On Fri, 2007-02-02 at 14:59 +0200, Rus V. Brushkoff wrote:
>> :> Yes, 2.6.19-1.6-04 (without nowcow) has the same problem. But the
>> :> interesting things is that reading /proc/interrupts in loop seems to
>> :> silently eat kernel memory by small chunks too. I'm now trying on a
>> :> vanilla kernel.
>> :Confirmed. A vanilla 2.6.19 silently eats memory when
>> :reading /proc/interrupts in loop. Mathias, could you please confirm this
>> :on your box too? TIA,
>>
>> Tested on K8 x86_64 SMP and K8 x86 UP : SMP system leaks memory, UP
>> doesn't.
>
> Thanks. I do have a leak on UP here though; vmstat or any other command
> do not eat this memory (at least neither ps or top report any continuous
> growth of their vm space while running the test), so I would wildly
> guess that's a kernel-based leakage occurring somewhere in the procfs
> support.
Must be .config-dependent. My UP box (.config attached) doesn't expose
any leak on /proc/interrupt loops with 2.6.19.2.
Jan
[-- Attachment #1.2: config.bz2 --]
[-- Type: application/octet-stream, Size: 7462 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-02-02 14:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 8:43 [Xenomai-help] Error: cat: /proc/xenomai/stat: Cannot allocate memory M. Koehrer
2007-02-02 9:33 ` Philippe Gerum
2007-02-02 9:49 ` Philippe Gerum
2007-02-02 9:51 ` Gilles Chanteperdrix
2007-02-02 11:23 ` Philippe Gerum
2007-02-02 12:44 ` Philippe Gerum
2007-02-02 12:58 ` Re: [Xenomai-help] Error: cat: /proc/xenomai/stat: Cannot allocate M. Koehrer
2007-02-02 14:35 ` Philippe Gerum
2007-02-02 12:59 ` [Xenomai-help] Error: cat: /proc/xenomai/stat: Cannot allocate memory Rus V. Brushkoff
2007-02-02 14:31 ` Philippe Gerum
2007-02-02 14:36 ` Rus V. Brushkoff
2007-02-03 16:08 ` Rus V. Brushkoff
2007-02-03 16:38 ` Philippe Gerum
2007-02-03 18:20 ` Dmitry Adamushko
2007-02-03 19:06 ` Philippe Gerum
2007-02-04 13:54 ` Dmitry Adamushko
2007-02-04 14:01 ` Dmitry Adamushko
2007-02-05 10:02 ` Rus V. Brushkoff
2007-02-05 16:05 ` Paul
2007-02-04 7:16 ` Rus V. Brushkoff
2007-02-04 9:12 ` Philippe Gerum
2007-02-03 23:20 ` Paul
2007-02-02 14:42 ` Jan Kiszka [this message]
2007-02-02 14:55 ` Paul
2007-02-02 15:07 ` Rus V. Brushkoff
2007-02-02 15:16 ` Philippe Gerum
2007-02-02 15:29 ` Philippe Gerum
2007-02-02 10:16 ` Re: [Xenomai-help] Error: cat: /proc/xenomai/stat: Cannot allocate M. Koehrer
2007-02-02 14:13 ` Re: Re: [Xenomai-help] Error: cat: /proc/xenomai/stat: Cannot M. Koehrer
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=45C34DEE.2020101@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--cc=rus@domain.hid \
--cc=xenomai@xenomai.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 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.