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: Wed, 13 Apr 2005 21:32:25 +0900	[thread overview]
Message-ID: <9b7ca65705041305327bd600f6@mail.gmail.com> (raw)
In-Reply-To: <20050413051326.GA12632@gate.ebshome.net>

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.

Actually, Im not too sure what is required to put something in kernel
in process context. Maybe its alot harder than I think it is...

> I think it's a bad idea. You are trying to workaround a problem
> instead of fixing it. My experience shows that sooner or later it'll
> come back and hit you anyway :).

I'm with you on this. It just that I didnt think putting my code in
process context would be regarded as workaround. Since kernel itself
ran fine, only after putting in my change it caused problem, I simply
thought that putting changes to code that was already there is more
severe than making further changes to what I've done. At least this
way, change is still within my domain.

But again, if putting my function in process context is that hard..
okay I better think otherwise :)

--=20
Daniel

  reply	other threads:[~2005-04-13 12:32 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 [this message]
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=9b7ca65705041305327bd600f6@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.