From: "Lee, Kuk-hyun" <errai110@kornet.net>
To: <netdev@oss.sgi.com>
Subject: [question] netif_rx() - why don't call raise_softirq()?
Date: Thu, 5 Feb 2004 04:11:58 +0900 [thread overview]
Message-ID: <004101c3eb52$c3412d20$5d03c5d3@errai> (raw)
Hi,
I am newbie in the latest kernel development. Nowadays I am starting to work in
linux kernel. BTW, I find kernel code that I can't understand.
in bellow.
netif_rx() in 2.4.19
1238 dev_hold(skb->dev);
1239 __skb_queue_tail(&queue->input_pkt_queue,skb);
1240 /* Runs from irqs or BH's, no need to wake BH */
1241 cpu_raise_softirq(this_cpu, NET_RX_SOFTIRQ);
1242 local_irq_restore(flags);
netif_rx() in 2.4.20
1254 dev_hold(skb->dev);
1255 __skb_queue_tail(&queue->input_pkt_queue,skb);
1256 local_irq_restore(flags);
why 2.4.20's netif_rx() don't call raise_softirq()? Is there never call net_rx_action()?
maybe, IMHO, because NAPI. but I want to know exactly. I don't know reason why should
you that. I could not find reason in google or netdev mailling list.
sorry for my stupid question. Any help is highly appriciated.
Thanks,
Lee
next reply other threads:[~2004-02-04 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 19:11 Lee, Kuk-hyun [this message]
[not found] <107592194524598240.1.ppp13@ppp13>
2004-02-05 3:39 ` [question] netif_rx() - why don't call raise_softirq()? Lee, Kuk Hyun
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='004101c3eb52$c3412d20$5d03c5d3@errai' \
--to=errai110@kornet.net \
--cc=netdev@oss.sgi.com \
/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).