From: "David S. Miller" <davem@redhat.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: jgarzik@pobox.com, akpm@osdl.org, netdev@oss.sgi.com, cramerj@intel.com
Subject: Re: Fw: Badness in local_bh_enable at kernel/softirq.c:119
Date: Wed, 1 Oct 2003 01:37:10 -0700 [thread overview]
Message-ID: <20031001013710.425038fd.davem@redhat.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E010124F0B1@orsmsx402.jf.intel.com>
On Wed, 1 Oct 2003 01:19:41 -0700
"Feldman, Scott" <scott.feldman@intel.com> wrote:
> Synchronizing on the hardware side is stumping me. We have the list of
> skbs you describe, but I'm concerned about unmapping the skb buffers if
> hardware is right in the middle of some DMA on one of the buffers.
> Some archs really don't like hardware accessing unmapped buffers.
Good point, if the e1000 accesses the DMA buffer after the unmap
it will cause many arch's to signal PCI errors since the IOMMU
will no longer have a valid translation for those DMA requests.
> Here's what I'm thinking: when link down is detected in the timer, just
> trick hardware into thinking link is still up (ILOS - Invert Loss of
> Signal). No locking, no disabling of interrupts. Hardware will do the
> natural thing by completing the outstanding sends and also provide the
> interrupts so we can clean/return skbs as normal (e1000_clean_tx_irq).
If you can make that work, it's the simplest fix.
next prev parent reply other threads:[~2003-10-01 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 8:19 Fw: Badness in local_bh_enable at kernel/softirq.c:119 Feldman, Scott
2003-10-01 8:37 ` David S. Miller [this message]
2003-10-01 14:40 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 17:27 Feldman, Scott
2003-10-01 6:51 ` David S. Miller
2003-09-29 21:36 Andrew Morton
2003-09-30 5:49 ` David S. Miller
2003-09-30 11:53 ` David S. Miller
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=20031001013710.425038fd.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@osdl.org \
--cc=cramerj@intel.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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).