From: Anton Blanchard <anton@samba.org>
To: Scott Feldman <sfeldma@pobox.com>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com, lunz@falooley.org
Subject: Re: [PATCH 2.6] e100: remove reference to NAPI config option
Date: Tue, 1 Feb 2005 12:43:58 +1100 [thread overview]
Message-ID: <20050201014358.GD15786@krispykreme.ozlabs.ibm.com> (raw)
In-Reply-To: <1107220952.3366.4.camel@sfeldma-mobl.dsl-verizon.net>
Hi Scott,
> e100 is NAPI all the time, so the Kconfig option is wasting space.
Speaking of NAPI...
We have seen issues with NAPI on ppc64 on various cards in the past.
Its possibly due to missing memory barriers; the interrupt and read of
the interrupt status provide syncronization with DMA on the non NAPI
case. Without this you need to be very careful to order reads (eg
between reading the ring status and the packet data).
Anton
next prev parent reply other threads:[~2005-02-01 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 1:22 [PATCH 2.6] e100: remove reference to NAPI config option Scott Feldman
2005-02-01 1:43 ` Anton Blanchard [this message]
2005-02-01 2:04 ` Scott Feldman
2005-02-01 14:25 ` John W. Linville
2005-02-02 5:29 ` Jeff Garzik
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=20050201014358.GD15786@krispykreme.ozlabs.ibm.com \
--to=anton@samba.org \
--cc=jgarzik@pobox.com \
--cc=lunz@falooley.org \
--cc=netdev@oss.sgi.com \
--cc=sfeldma@pobox.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).