From: Stephen Hemminger <shemminger@vyatta.com>
To: "Hector Herrera" <mail4hh@imagen.ca>
Cc: netdev@vger.kernel.org
Subject: Re: rt_cache leak 2.6.18
Date: Tue, 17 Feb 2009 20:10:59 -0800 [thread overview]
Message-ID: <20090217201059.558411a1@extreme> (raw)
In-Reply-To: <3496.64.46.62.42.1234920235.squirrel@webmail.imagen.ca>
On Tue, 17 Feb 2009 17:23:55 -0800 (PST)
"Hector Herrera" <mail4hh@imagen.ca> wrote:
> Hello,
>
> I'm debugging an rt_cache leak in 2.6.18 and I would like to view the
> memory contents of the leaked memory slab with the hopes that if I knew
> which routes are being leaked then I would know which network traffic to
> collect to be able to reproduce the leak in a test environment.
>
> I would appreciate any suggestions you could give me with regards to how
> to go about doing this (searching google didn't turn out anything too
> helpful).
>
> Thank you,
>
> Hector
>
That was 2 1/2 years ago! If you want to do software archeology, they you
really have to do it yourself. Otherwise, please confirm problem on more
recent version.
prev parent reply other threads:[~2009-02-18 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 1:23 rt_cache leak 2.6.18 Hector Herrera
2009-02-18 4:10 ` Stephen Hemminger [this message]
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=20090217201059.558411a1@extreme \
--to=shemminger@vyatta.com \
--cc=mail4hh@imagen.ca \
--cc=netdev@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).