linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: erik@hensema.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0: something is leaking memory
Date: 04 Jan 2004 13:39:22 -0800	[thread overview]
Message-ID: <52wu87wfzp.fsf@topspin.com> (raw)
In-Reply-To: <slrnbvh1hd.jl6.erik@dexter.hensema.net>

Yup, looks like IPv6 is leaking memory (since your netstat shows
nowhere near 19K sockets):

 > tcp6_sock          19729  19732   1024    4    1 : tunables   54   27    0 : slabdata   4933   4933      0

Now to figure out why...

 - R.

  reply	other threads:[~2004-01-04 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04 18:57 2.6.0: something is leaking memory Erik Hensema
2004-01-04 21:00 ` Linus Torvalds
2004-01-04 21:31   ` Erik Hensema
2004-01-04 21:39     ` Roland Dreier [this message]
2004-01-05 16:18       ` Ricky Beam
2004-01-05 18:16         ` Erik Hensema
2004-01-05  4:52     ` (usagi-core 16947) " YOSHIFUJI Hideaki / 吉藤英明
2004-01-04 23:18 ` Mike Fedyk

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=52wu87wfzp.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=erik@hensema.net \
    --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;
as well as URLs for NNTP newsgroup(s).