From: Alexander Puchmayr <alexander.puchmayr@jk.uni-linz.ac.at>
To: linux-kernel@vger.kernel.org
Subject: Memory leak in 2.4.5??
Date: Mon, 18 Jun 2001 10:22:15 +0200 [thread overview]
Message-ID: <01061810221500.01280@at18> (raw)
Hi folks!
When I try to copy large files (let say some iso-image or disk image) over
the network (regardless if nfs, ftp, whatever), the system starts to swap
until it stucks - RESET required.
It is impossible for me to get one large 300MB file to my local harddrive!!
Observations I made:
* No process seems to allocate the memory, buffered/cached memory is very
low. So I assume that the kernel "eats" the memory.
* I tried my tests with a 100 MBit card (3c905) and a 10 MBit card (rtl-8029
based), and it appeared only with the 100MBps card.
The kernel I'm using is a vanilla 2.4.5 with knfsd-patch (from namesys).
Thanks
Alexander Puchmayr
--
---
Alexander Puchmayr
Institut für Theoretische Physik Altenbergerstr. 69, A-4040 Linz
Johannes-Kepler Universitaet Phone: ++43 732/2468-8633
A-4040 Linz, Austria Fax: ++43 732/2468-8585
E-Mail: alexander.puchmayr@jk.uni-linz.ac.at
reply other threads:[~2001-06-18 8:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=01061810221500.01280@at18 \
--to=alexander.puchmayr@jk.uni-linz.ac.at \
--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