| To: | Bart Trojanowski <bart@xxxxxxxxx> |
|---|---|
| Subject: | Re: skb allocation problems (More Brain damage!) |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Wed, 11 Apr 2001 20:25:12 +0200 |
| Cc: | Imran.Patel@xxxxxxxxx, ak@xxxxxxx, netfilter-devel@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <Pine.LNX.4.30.0104111343380.31460-100000@localhost>; from bart@jukie.net on Wed, Apr 11, 2001 at 01:47:18PM -0400 |
| References: | <2D6CADE9B0C6D411A27500508BB3CBD063CF2D@eseis15nok> <Pine.LNX.4.30.0104111343380.31460-100000@localhost> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Wed, Apr 11, 2001 at 01:47:18PM -0400, Bart Trojanowski wrote:
>
> Coudl the problem be in the NIC driver not in the alloc_skb? I have used
> both 2.4.{1,3} for some time and never seen this corruption. I use ping
> -f with various packet sizes for stress testing my IPSec boxes... these do
> quite a bit of extra skb creation as an IPSec header sometimes does not
> fit in the original skb. No problems yet.
>
> My gut tells me to blame the NIC driver of the NIC itself.
The NIC is not directly involved in alloc_skb() (except maybe if it corrupts
internal data structures of the allocator)
-Andi
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: skb allocation problems (More Brain damage!), Imran . Patel |
|---|---|
| Next by Date: | Re: skb allocation problems (More Brain damage!), Andi Kleen |
| Previous by Thread: | RE: skb allocation problems (More Brain damage!), Bart Trojanowski |
| Next by Thread: | Re: skb allocation problems (More Brain damage!), Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |