All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 14 Apr 2005 21:36:24 +0900	[thread overview]
Message-ID: <9b7ca657050414053650cc817@mail.gmail.com> (raw)
In-Reply-To: <9b7ca65705041305327bd600f6@mail.gmail.com>

On 4/13/05, Eugene Surovegin <ebs@ebshome.net> wrote:
> Then do it. It should be trivial to unwind the stack and much simpler
> than moving this code to process context.

You know what ?? You were right about it being trivial. Didnt take me
to too long to find the line and saw what was going on.
Initially I started reading on how to put the line in process context,
but soon I realised its not something you want to spend your afternoon
on :P (Currently I dont have too many afternoons for this)

Anyway, thanks for the pointer.

Actual problem came from rtnetlink.c file where it called
rtmsg_ifinfo(). This in turn, called alloc_skb with GFP_KERNEL, rather
an GFP_ATOMIC. I guess GFP_KERNEL is right, but what's the difference
?

--=20
Daniel

  reply	other threads:[~2005-04-14 12:36 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
2005-04-13  5:13     ` Eugene Surovegin
2005-04-13 12:32       ` Daniel Ann
2005-04-14 12:36         ` Daniel Ann [this message]
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=9b7ca657050414053650cc817@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.