Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Harald Koerfgen <hkoerfg@web.de>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Dave Airlie <airlied@csn.ul.ie>
Cc: Ralf Baechle <ralf@uni-koblenz.de>,
	linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: [patch] linux: declance multicast filter fixes
Date: Wed, 27 Mar 2002 22:20:46 +0100	[thread overview]
Message-ID: <E16qKqX-00062M-00@smtp.web.de> (raw)
In-Reply-To: <Pine.GSO.3.96.1020325123322.4605A-100000@delta.ds2.pg.gda.pl>

Hi,

On Monday 25 March 2002 12:40, Maciej W. Rozycki wrote:
>  Well, the core seems to be already separated -- see drivers/net/7990.c.
> I haven't yet checked how suitable it is and many front-end drivers use it
> already.
>
>  For the I/O ASIC front-end I'm going to check if the ASIC is capable of
> mapping the LANCE more sensibly before starting any further work.  The
> current configuration is a major loss, doubling the CPU's work and I can't
> see any reasonable explanation for such a setup.

It's been quite some time since I have hacked the declance driver and I don't 
remember all the details, so take the following with a grain of salt.

The 7990 is basically a 16-bit chip in a 32-bit environment, and, AFAIR, uses 
two different DMA modes to access host memory. One is a 16-bit word-by-word 
access for the ring descriptors and the other is 8 16-bit-words-bursts for 
accessing the ring buffers themselves, where the LANCE only generates one 
target address per burst.

The IOASIC is, just as the CPU, only capable of doing 32-bit transfers 
to/from memory. So 16-bit LANCE accesses are translated into 32-bit IOASIC 
accesses but a part of the DMA target addresses are generated by the LANCE.

This leads to a 16-bit -> 32-bit mapping for the ring descriptors and a 
8*16-bit -> 8*32-bit mapping for ring buffers. Very efficient :-(.

Greetings,
Harald

  reply	other threads:[~2002-03-27 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21 18:04 [patch] linux: declance multicast filter fixes Maciej W. Rozycki
2002-03-22 11:08 ` Dave Airlie
2002-03-22 11:08   ` Dave Airlie
2002-03-23 14:01   ` Maciej W. Rozycki
2002-03-24 13:51     ` Dave Airlie
2002-03-24 13:51       ` Dave Airlie
2002-03-25 11:40       ` Maciej W. Rozycki
2002-03-27 21:20         ` Harald Koerfgen [this message]
2002-03-28 13:01           ` Maciej W. Rozycki
2002-03-29  7:57             ` Harald Koerfgen

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=E16qKqX-00062M-00@smtp.web.de \
    --to=hkoerfg@web.de \
    --cc=airlied@csn.ul.ie \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ralf@uni-koblenz.de \
    /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