linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 09:51:16 -0400	[thread overview]
Message-ID: <20050412135114.GB27920@tuxdriver.com> (raw)
In-Reply-To: <9b7ca657050412060556af952e@mail.gmail.com>

On Tue, Apr 12, 2005 at 10:05:14PM +0900, Daniel Ann wrote:
> On Apr 12, 2005 9:24 PM, John W. Linville <linville@tuxdriver.com> wrote:
> > You may want to consider dev_alloc_skb...
> 
> Ahh that's right. I remember reading a little comment on top dev_alloc_skb().
> Thank you so much. At least that inspired me :)
> 
> Thing is, I got this error during a call to notifier_call_chain. So..

My guess would be that your best bet is to move your call to
notifier_call_chain off to a workqueue.  notifier_call_chain (and/or
one or more of the functions it is calling) is likely written to
expect to be in process context.

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2005-04-12 13:51 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
2005-04-12 13:05   ` Daniel Ann
2005-04-12 13:51     ` John W. Linville [this message]
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=20050412135114.GB27920@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=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 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).