From: Wojciech Kromer <krom@dgt-lab.com.pl>
To: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: cd
Date: Tue, 06 Jan 2004 08:47:57 +0100 [thread overview]
Message-ID: <3FFA682D.1030402@dgt-lab.com.pl> (raw)
In-Reply-To: <200401052252.QAA10493@lists.linuxppc.org>
Użytkownik Samo Pogacnik napisał:
>On Monday 05 January 2004 09:15, Wojciech Kromer wrote:
>
>
>>Użytkownik Samo Pogacnik napisał:
>>
>>
>>>Is it possible that there is something wrong in the way how the:
>>>"netif_wake_queue(dev)" gets called from the interrupt handler in the
>>>"fcc_enet.c"? I can confirm this problem for 2.4.18 as well as 2.6.0
>>>kernels on mpc82xx.
>>>
>>>
>>i don't know exactly what's wrong with 82xx code, but i wrote a small
>>patch that frees unfreed skbuf before allocating new one, and now it
>>works fine
>>
>>additionaly, i had no problem with (almost) the same code on 8xx
>>
>>
>
>hi, Wojciech
>can you send the patch?
>
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
>by, Samo
>
>
here it is:
--------------------------------------------------------------------------------------------------------
***************
*** 413,418 ****
--- 412,420 ----
/* Save skb pointer.
*/
+ //by k@m 2003-12-05
+ if(cep->tx_skbuff[cep->skb_cur])
+ dev_kfree_skb_irq (cep->tx_skbuff[cep->skb_cur]);
cep->tx_skbuff[cep->skb_cur] = skb;
cep->stats.tx_bytes += skb->len;
***************
*** 560,565 ****
--- 562,568 ----
/* Free the sk buffer associated with this last transmit.
*/
dev_kfree_skb_irq(cep->tx_skbuff[cep->skb_dirty]);
+ cep->tx_skbuff[cep->skb_dirty]=0;//by k@m 2003-12-05
cep->skb_dirty = (cep->skb_dirty + 1) & TX_RING_MOD_MASK;
/* Update pointer to next buffer descriptor to be transmitted.
***************
*** 1348,1353 ****
--- 1351,1357 ----
* It works when I do this.
*/
memset((char *)ep, 0, sizeof(fcc_enet_t));
+ memset(cep->tx_skbuff,0,sizeof(cep->tx_skbuff));
/* Allocate space for the buffer descriptors in the DP ram.
* These are relative offsets in the DP ram address space.
-------------------------------------------------------------------------------------------
ps: i send you my full version of fcc_enet.c
--
* * * * * * * * * * * *
* per pedes ad astra! *
* * * * * * * * * * * * mailto:krom@dgt-lab.com.pl
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-06 7:47 UTC|newest]
Thread overview: 7+ 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 ` Wojciech Kromer [this message]
2004-01-06 22:03 ` Samo Pogacnik
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 14:49 cd jpinheiro
2013-04-03 22:55 ` cd Andreas Ericsson
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=3FFA682D.1030402@dgt-lab.com.pl \
--to=krom@dgt-lab.com.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.