From: "David S. Miller" <davem@redhat.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: net_device->queue_lock contention on 32-way box
Date: Wed, 26 May 2004 15:00:40 -0700 [thread overview]
Message-ID: <20040526150040.25b9ec51.davem@redhat.com> (raw)
In-Reply-To: <200405262147.i4QLlFF23657@unix-os.sc.intel.com>
On Wed, 26 May 2004 14:47:15 -0700
"Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
> Could netif_schedule() take long time to run?
No, it's a series of a few atomic operations.
1) test_and_set_bit()
2) disable cpu interrupts
3) Link list insertion
4) Set a local-cpu flag
5) re-enable cpu interrupts
prev parent reply other threads:[~2004-05-26 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 20:47 Chen, Kenneth W
2004-05-26 20:54 ` David S. Miller
2004-05-26 21:47 ` Chen, Kenneth W
2004-05-26 22:00 ` David S. Miller [this message]
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=20040526150040.25b9ec51.davem@redhat.com \
--to=davem@redhat.com \
--cc=kenneth.w.chen@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®