From: Greg Banks <gnb@melbourne.sgi.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Linux Network Development list <netdev@oss.sgi.com>
Subject: Re: Locking model for NAPI drivers
Date: Wed, 01 Jun 2005 18:16:36 +1000 [thread overview]
Message-ID: <1117613796.26331.2479.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <20050531.154847.63995530.davem@davemloft.net>
On Wed, 2005-06-01 at 08:48, David S. Miller wrote:
> So the idea is, if we can make all of the spinlocks BH locks we'll
> solve a whole bunch of problems:
> [...]
> 2) the driver will actually produce useful profiling data
> via oprofile and friends since timer interrupts will run
> even while holding the locks
That would be really, really nice.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
next prev parent reply other threads:[~2005-06-01 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 22:48 Locking model for NAPI drivers David S. Miller
2005-06-01 6:28 ` Andi Kleen
2005-06-01 8:42 ` Herbert Xu
2005-06-01 8:16 ` Greg Banks [this message]
2005-06-01 20:33 ` Michael Chan
2005-06-01 22:21 ` David S. Miller
2005-06-01 21:34 ` Michael Chan
2005-06-02 19:56 ` Michael Chan
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=1117613796.26331.2479.camel@hole.melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=davem@davemloft.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).