From: Daniel Ann <ktdann@gmail•com>
To: Daniel Ann <ktdann@gmail•com>,
linuxppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: Trying to understand alloc_skb()
Date: Wed, 13 Apr 2005 13:50:05 +0900 [thread overview]
Message-ID: <9b7ca657050412215025872ce3@mail.gmail.com> (raw)
In-Reply-To: <20050412161230.GA18567@gate.ebshome.net>
On 4/13/05, Eugene Surovegin <ebs@ebshome•net> wrote:
> You don't need any locks, just pass correct gfp_mask parameter to
> alloc_skb when it's called from IRQ context, e.g. GFP_ATOMIC.
Thing is, I'm not actually calling alloc_skb directly from my
function. I'm calling notifier_call_chain() and somehow inadvertently
it is getting called. If I was to give GFP_ATOMIC, then I'd have to
first find the code that is responsible.
Reading what John said earlier, rather than trying to find the code
that is calling alloc_skb, I should be moving the calls to my
fnuctions into process context.
So.. I'm gonna go ahead with John's suggestion.. but only problem now
is how do I move it to process context :P (May be more importantly,
how do I know that the code needs to be in process context or not?
which will prevent further headaches and possible coding a time bomb
:) )
--=20
Daniel
next prev parent reply other threads:[~2005-04-13 4: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
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 [this message]
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=9b7ca657050412215025872ce3@mail.gmail.com \
--to=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