* rt_cache leak 2.6.18
@ 2009-02-18 1:23 Hector Herrera
2009-02-18 4:10 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Hector Herrera @ 2009-02-18 1:23 UTC (permalink / raw)
To: netdev
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: rt_cache leak 2.6.18
2009-02-18 1:23 rt_cache leak 2.6.18 Hector Herrera
@ 2009-02-18 4:10 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2009-02-18 4:10 UTC (permalink / raw)
To: Hector Herrera; +Cc: netdev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-02-18 4:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-18 1:23 rt_cache leak 2.6.18 Hector Herrera
2009-02-18 4:10 ` Stephen Hemminger
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).