From: Samo Pogacnik <samo.pogacnik@s5.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: memory problem with fec on 8250
Date: Tue, 6 Jan 2004 23:03:14 +0100 [thread overview]
Message-ID: <200401062203.QAA15156@lists.linuxppc.org> (raw)
In-Reply-To: <3FFA682D.1030402@dgt-lab.com.pl>
On Tuesday 06 January 2004 08:47, Wojciech Kromer wrote:
> sure, just 4 lines addes
>
> >did you free skbuffs from the irq handler or somewhere else?
>
> just before allocation
>
> >when i run netperf (snapshot) test using the 100Mbps connection, this
> >test eats all the available RAM. the /proc/meminfo shows that most
> >of the used memory at that point is been held by internal kernel
> >structures (Slab).
>
> better reults are shwn with grep skb /proc/slabinfo
>
> here it is:
.
.
.
Thank you for the tips and the patch.
Eth seems to be working now without eating the RAM.
By the way that you have solved the problem, I suspect that BDs are written
over the dirty_tx limit, before their associated skbs get freed via the irq
handler.
bye, Samo
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-06 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 15:55 memory problem with fec on 8250 Samo Pogacnik
2004-01-05 8:15 ` Wojciech Kromer
2004-01-05 22:52 ` Samo Pogacnik
2004-01-06 7:47 ` cd Wojciech Kromer
2004-01-06 22:03 ` Samo Pogacnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 7:48 memory problem with fec on 8250 Kromer
2003-12-04 8:45 ` Wojciech Kromer
2003-12-04 9:15 ` Eugene Surovegin
2003-12-04 9:45 ` Wojciech Kromer
2003-12-04 10:19 ` Eugene Surovegin
[not found] ` <3FCF0E68.4010303@dgt-lab.com.pl>
[not found] ` <20031204105532.GA2065@gate.ebshome.net>
2003-12-04 11:25 ` Wojciech Kromer
2003-12-04 14:03 ` Dan Malek
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=200401062203.QAA15156@lists.linuxppc.org \
--to=samo.pogacnik@s5.net \
--cc=linuxppc-embedded@lists.linuxppc.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).