public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dipak <dipak@monmouth.com>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Leak in network memory?
Date: Wed, 08 Aug 2001 08:49:10 -0400	[thread overview]
Message-ID: <3B713546.C2023EDC@monmouth.com> (raw)
In-Reply-To: <200108022222.CAA00348@mops.inr.ac.ru>

Hi,
    I'm facing the effect of memory leak most probably. I've compiled 2.4.1
kernel. When I leave my m/c running overnight, I used to find the m/c has
become very slow. Any command from shell prompt takes too much of time to
execute. I don't have any other option but to reboot, which also takes too
much time to actually shutdown the m/c before re-booting. I've compiled the
2.4.1 kernel on 2.2.14 of RedHat 6.2 release.
    As I've no mail in follow-up of the following mail in this mailing-list,
I have no idea of what solution anybody had come up with if it is really a
memory leakage problem. Please help me in this regard.

Thanks in advance,
Dipak

Alexey Kuznetsov wrote:

> Hello!
>
> > buffers of sockets. All sockets are set to have 64KB (the default)
>
> Are you sure? Default is 16K.
>
> Alexey
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2001-08-08 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30  3:27 Leak in network memory? William M. Shubert
2001-07-30 14:46 ` Matthew G. Marsh
2001-07-31  1:40   ` William M. Shubert
2001-08-02 22:22 ` Alexey Kuznetsov
2001-08-08 12:49   ` Dipak [this message]
2001-08-08 13:54     ` David S. Miller

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=3B713546.C2023EDC@monmouth.com \
    --to=dipak@monmouth.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --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