public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	alexander.eichhorn@rz.tu-ilmenau.de,
	linux-kernel@vger.kernel.org
Subject: Re: [Question] Explanation of zero-copy networking
Date: 09 May 2001 09:13:36 -0600	[thread overview]
Message-ID: <m1k83qlfmn.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E14wlUi-0003WQ-00@the-village.bc.nu> <Pine.LNX.3.95.1010507121212.4256A-100000@chaos.analogic.com> <20010508091811.C17720@pcep-jamie.cern.ch>
In-Reply-To: Jamie Lokier's message of "Tue, 8 May 2001 09:18:11 +0200"

Jamie Lokier <lk@tantalophile.demon.co.uk> writes:

> Richard B. Johnson wrote:
> > However, PCI to memory copying runs at about 300 megabytes per
> > second on modern PCs and memory to memory copying runs at over 1,000
> > megabytes per second. In the future, these speeds will increase.
> 
> That would be "big expensive modern PCs" then.  Our clusters of 700MHz
> boxes are strictly limited to 132 megabytes per second over PCI...

300 Megabytes per second is definitely an odd number for a PCI bus.
But 132 Megabytes per second is actually high, the continuous burst
speeds are:
32bit 33Mhz: 33*1000*1000*32/(1024*1024*8) = 125.8 Megabytes/second
64bit 33Mhz: 33*1000*1000*64/(1024*1024*8) = 251.7 Megabytes/second
32bit 66Mhz: 66*1000*1000*32/(1024*1024*8) = 251.7 Megabytes/second
64bit 66Mhz: 66*1000*1000*64/(1024*1024*8) = 503.4 Megabytes/second

The possibility of getting a continuous bursts is actually low, if
nothing else you have an interrupt acknowledgement 100 times per
second.  But if you are pushing the bus it should deliver close to
it's burst potential.  But the ISA traffic doing subtractive decode
can be nasty because you get 4 PCI cycles before you even get
acknowledgement from the PCI/ISA bridge that you there is something to
transfer to.   

Eric

  reply	other threads:[~2001-05-13 15:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-07 13:43 [Question] Explanation of zero-copy networking Alexander Eichhorn
2001-05-07 13:56 ` Alan Cox
2001-05-07 16:12   ` Richard B. Johnson
2001-05-07 17:53     ` Francois Romieu
2001-05-07 18:00       ` Blue Lang
2001-05-07 18:25     ` dean gaudet
2001-05-07 19:54       ` Richard B. Johnson
2001-05-07 20:23         ` dean gaudet
2001-05-08 11:09         ` Bjorn Wesen
2001-05-08 17:30         ` Alexander Eichhorn
2001-05-09  9:56           ` Reto Baettig
2001-05-07 18:30     ` Pekka Pietikainen
2001-05-07 19:00       ` Venkatesh Ramamurthy
2001-05-08  7:18     ` Jamie Lokier
2001-05-09 15:13       ` Eric W. Biederman [this message]
2001-05-07 18:21   ` dean gaudet
2001-05-07 21:59     ` Alan Cox
2001-05-08 16:20       ` Jamie Lokier

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=m1k83qlfmn.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alexander.eichhorn@rz.tu-ilmenau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=root@chaos.analogic.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