From: Daniel Ann <ktdann@gmail.com>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Trying to understand alloc_skb()
Date: Tue, 12 Apr 2005 17:49:59 +0900 [thread overview]
Message-ID: <9b7ca657050412014971db02a7@mail.gmail.com> (raw)
In-Reply-To: <9b7ca6570504120138738b554f@mail.gmail.com>
In addition,
Im running 2.4.21 kernel.
Just then, I was looking at the 2.6.11 kernel source
(net/core/skbuff.c) and found out that large chunk of the alloc_skb()
has been thrown out.
Can this be removed from 2.4.21 also ? I might go and check out why
its been removed.
Still waiting for some good answer tho .. :)
Cheers,
On Apr 12, 2005 5:38 PM, Daniel Ann <ktdann@gmail.com> wrote:
> Hiya folks,
>
> I'm wondering if anyone could help me out with problem I have in alloc_skb().
>
> My problem is that, kernel dies with "alloc_skb called nonatomically
> from interrupt c00ba718" message. After browsing mailing list, I think
> its to do with not providing it with enough locks prior.
>
> Question is, what kind of lock should I be providing ?
>
> Since I have no clue as to which lock does what, I really need some
> good advise as to where to start looking.
>
> Could someone tell me the inside story on this ?
>
> --
> Daniel
>
--
Daniel
next prev parent reply other threads:[~2005-04-12 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 8:38 Trying to understand alloc_skb() Daniel Ann
2005-04-12 8:49 ` Daniel Ann [this message]
2005-04-12 12:24 ` John W. Linville
2005-04-12 13:05 ` Daniel Ann
2005-04-12 13:51 ` John W. Linville
2005-04-13 4:40 ` Daniel Ann
2005-04-12 16:12 ` Eugene Surovegin
2005-04-13 4:50 ` Daniel Ann
2005-04-13 5:13 ` Eugene Surovegin
2005-04-13 12:32 ` Daniel Ann
2005-04-14 12:36 ` Daniel Ann
2005-04-13 6:05 ` Donald White
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=9b7ca657050412014971db02a7@mail.gmail.com \
--to=ktdann@gmail.com \
--cc=linuxppc-embedded@ozlabs.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.