From: "John W. Linville" <linville@tuxdriver•com>
To: Daniel Ann <ktdann@gmail•com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: Trying to understand alloc_skb()
Date: Tue, 12 Apr 2005 08:24:07 -0400 [thread overview]
Message-ID: <20050412122405.GA27920@tuxdriver.com> (raw)
In-Reply-To: <9b7ca6570504120138738b554f@mail.gmail.com>
On Tue, Apr 12, 2005 at 05:38:01PM +0900, Daniel Ann wrote:
> 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.
You may want to consider dev_alloc_skb...
--
John W. Linville
linville@tuxdriver•com
next prev parent reply other threads:[~2005-04-12 13:22 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
2005-04-12 12:24 ` John W. Linville [this message]
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=20050412122405.GA27920@tuxdriver.com \
--to=linville@tuxdriver$(echo .)com \
--cc=ktdann@gmail$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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