From: Andrey Savochkin <saw@saw.sw.com.sg>
To: "David S. Miller" <davem@redhat.com>
Cc: fxzhang@ict.ac.cn, linux-mips@oss.sgi.com,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
jgarzik@mandrakesoft.com
Subject: Re: NAPI for eepro100
Date: Thu, 13 Jun 2002 12:57:53 +0400 [thread overview]
Message-ID: <ae9md0$mm1$2@main.gmane.org> (raw)
In-Reply-To: <20020612.160532.134201977.davem@redhat.com>; from "David S. Miller" on Wed, Jun 12, 2002 at 04:05:32PM
On Wed, Jun 12, 2002 at 04:05:32PM -0700, David S. Miller wrote:
> From: Jeff Garzik <jgarzik@mandrakesoft.com>
> Date: Wed, 12 Jun 2002 19:00:00 -0400
>
> for the 'mips' patch, it looks
> like the arch maintainer(s) need to fix the PCI DMA support...
>
> No, it's worse than that.
>
> See how non-consistent memory is used by the eepro100 driver
> for descriptor bits? The skb->tail bits?
>
> That is very problematic.
What's the problem?
If it isn't allowed to do, then what is the meaning of PCI_DMA_BIDIRECTIONAL
mappings?
Andrey
next prev parent reply other threads:[~2002-06-13 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D0740ED.2060907@ict.ac.cn>
2002-06-12 23:00 ` NAPI for eepro100 Jeff Garzik
[not found] ` <3D07D270.5060902@mandrakesoft.com>
2002-06-12 23:05 ` David S. Miller
[not found] ` <20020612.160532.134201977.davem@redhat.com>
2002-06-12 23:17 ` Jeff Garzik
[not found] ` <3D07D6A6.7090308@mandrakesoft.com>
2002-06-12 23:33 ` David S. Miller
[not found] ` <20020613125753.A23693@castle.nmd.msu.ru>
2002-06-13 8:47 ` David S. Miller
2002-06-13 8:57 ` Andrey Savochkin [this message]
[not found] <20020612.163344.31410429.davem@redhat.com>
2002-06-13 2:25 ` Donald Becker
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='ae9md0$mm1$2@main.gmane.org' \
--to=saw@saw.sw.com.sg \
--cc=davem@redhat.com \
--cc=fxzhang@ict.ac.cn \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@oss.sgi.com \
--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).