All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Stewart <joshua.stewart@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: From __cpu_raise_softirq() to net_rx_action()
Date: Sun, 22 Dec 2002 16:11:37 -0500	[thread overview]
Message-ID: <1040591503.11608.6.camel@localhost.localdomain> (raw)

I'm still trying to follow a packet (or even better an sk_buff) from the
NIC card to user space.  I think I have a good chunk of it figured out,
but I'm missing a bit from the time that the __netif_rx_schedule()
routine calls __cpu_raise_softirq() until the routine net_rx_action()
occurs.  I read in a book on Linux TCP/IP implementation that the
softirq basically leads to a call to net_rx_action(), but I don't see
the connection yet.  It's probably due to my lack of understanding of
IRQ's (and software IRQ's).

Any help is appreciated.

Thanks,
	Josh 




             reply	other threads:[~2002-12-22 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-22 21:11 Joshua Stewart [this message]
2002-12-22 21:15 ` From __cpu_raise_softirq() to net_rx_action() Randy.Dunlap
2002-12-22 21:35   ` Joshua Stewart
2002-12-22 21:31     ` Randy.Dunlap
2002-12-22 21:36 ` Arnaldo Carvalho de Melo

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=1040591503.11608.6.camel@localhost.localdomain \
    --to=joshua.stewart@comcast.net \
    --cc=linux-kernel@vger.kernel.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.