linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: tegeran@home.com
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Encrypted Swap
Date: 18 Aug 2001 06:32:26 -0600	[thread overview]
Message-ID: <m1elq9o8f9.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0108171200510.4065-100000@anime.net> <m1snepoft6.fsf@frodo.biederman.org> <01081803242800.00266@c779218-a>
In-Reply-To: <01081803242800.00266@c779218-a>

Nicholas Knight <tegeran@home.com> writes:

> On Saturday 18 August 2001 02:52 am, Eric W. Biederman wrote:
> > Dan Hollis <goemon@anime.net> writes:
> > > On 17 Aug 2001, Eric W. Biederman wrote:
> > > > Clearing memory on most machines takes a 1s or less.  Think of
> > > > memory fill rates at the 800MB/s level.  Most BIOS's seem to clear
> > > > some of the memory but I haven't read their code to see what they
> > > > are doing.
> > >
> > > Ive measured rates far lower than that, at least for SDRAM.
> >
> > Hmm.  The numbers were off the top of my head and I've been messing
> > with DDR SDRAM quite a bit so I may have doubled it.   Hmm.
> >
> > Nope.  I was remember something close to the typical streams numbers
> > on an Athlon with DDR SDRAM.  Since those are read-modify-write
> > numbers they should be close to the write numbers for normal SDRAM.
> >
> > With a PII/PIII and PC100 SDRAM I have measured about 640 MB/s writes.
> >
> 
> I'm not sure where you're pulling these numbers from, but being a 
> hardcore FPS gamer, I can tell you from experience, PC100 SDRAM does NOT 
> hit 640MB/sec! Esspecialy not on a PII! PC100 SDRAM on my current 800Mhz 
> non-tbird Athlon currently peaks near 250MB/sec

The actual tests results are somewhere at the office, but the figures are
in the right ballbark.  I'm not saying this is a common case, or easy
to get.  640 maybe be a little high but I know it was over 600MB/s. 
With carefully tuned code this is what you can get.  

Basically setting up an MTRR that does write-combining, on the area of
memory you are talking about so that you do not go through the cache.
Then something like ``xorl %eax, %eax; movl $0x1000000; rep stosl''
should achieve that kind of fill rate.  I have watched it on a logic
analyzer connected to instrumented DIMMs.  So I know it was making all
of the way to the RAM.  

You should be able to make it to SDRAM through the cache at this kind
of speed as well, but that wasn't the case I was interested at the
time I made the test.

When I performed the experiment I know it was a processor running the
P6 core and running on the l440GX motherboard, and that the memory
was PC100.

Between 600MB/s and 700MB/s is the theoretical peak of writes
on PC100 SDRAM.  So you can't do much better.  On the other hand you
should be coming much closer than 250MB/s.

The actually calculation for PC100 SDRAM using a burst length of 8 and
never refreshing goes like this.   There is one additional clock used
for the command byte on the SDRAM bus.
100*1000*1000hz * 8 bytes per clock * 8/9 / (1024*1024)  == 678 MB/s


Eric

  reply	other threads:[~2001-08-18 12:39 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 17:10 Encrypted Swap David Christensen
2001-08-17 17:21 ` Richard B. Johnson
2001-08-17 18:41   ` Eric W. Biederman
2001-08-17 19:05     ` Dan Hollis
2001-08-18  9:52       ` Eric W. Biederman
2001-08-18 10:24         ` Nicholas Knight
2001-08-18 12:32           ` Eric W. Biederman [this message]
2001-08-17 19:20     ` Richard B. Johnson
2001-08-18 10:34       ` Eric W. Biederman
     [not found] <fa.kmbqblv.v3uvig@ifi.uio.no>
2001-08-18 14:53 ` Ted Unangst
2001-08-18 15:17   ` Mr. James W. Laferriere
2001-08-20 11:03   ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2001-08-07 21:40 encrypted swap David Spreen
2001-08-07 18:53 Torrey Hoffman
2001-08-07 19:15 ` Thomas Pornin
2001-08-07 19:23 ` Dan Podeanu
2001-08-07 19:48   ` Andreas Dilger
2001-08-07 20:04   ` Marty Poulin
2001-08-07 21:06   ` David Wagner
2001-08-07 21:56     ` D. Stimits
2001-08-07 21:44   ` Pavel Machek
2001-08-07 19:48 ` Justin Guyett
2001-08-07 20:05   ` Alan Cox
2001-08-07 20:17   ` Bill Rugolsky Jr.
2001-08-07 17:30 Encrypted Swap David Maynor
2001-08-07 17:27 ` Rik van Riel
2001-08-07 15:28 encrypted swap David Maynor
2001-08-07 15:51 ` Florian Weimer
2001-08-07 15:06 David Maynor
2001-08-07 15:11 ` Florian Weimer
2001-08-07 15:43   ` Joel Jaeggli
2001-08-07 15:30 ` Garett Spencley
2001-08-07 16:21 ` David Spreen
2001-08-08  8:11 ` Helge Hafting
2001-08-07 14:37 David Maynor
2001-08-07 14:48 ` Billy Harvey
2001-08-07 16:03 ` Chris Wedgwood
     [not found] <no.id>
2001-08-07 14:17 ` Encrypted Swap Alan Cox
2001-08-07 15:16   ` Crutcher Dunnavant
2001-08-07 16:01     ` Chris Wedgwood
2001-08-07  2:28 David Spreen
2001-08-07  3:56 ` Justin Guyett
2001-08-07  4:01   ` Chris Wedgwood
2001-08-07  4:23   ` John Polyakov
2001-08-07  4:36     ` Chris Wedgwood
2001-08-07  5:12     ` Garett Spencley
2001-08-07  5:55       ` Ryan Mack
2001-08-07 12:37         ` Michael Bacarella
2001-08-17 14:50         ` Holger Lubitz
2001-08-17 15:39           ` Richard B. Johnson
2001-08-17 15:57             ` Holger Lubitz
2001-08-17 16:34               ` Gerhard Mack
2001-08-17 16:50               ` Richard B. Johnson
2001-08-17 17:06             ` Adrian Cox
2001-08-17 17:16               ` Richard B. Johnson
2001-08-17 17:22                 ` Jacob Alifrangis
2001-08-17 17:36                 ` Adrian Cox
2001-08-17 18:51                   ` Nicholas Knight
2001-08-17 19:30                     ` Richard B. Johnson
2001-08-18  8:51                       ` Adrian Cox
2001-08-18 11:02                         ` Eric W. Biederman
2001-08-19  8:51                           ` Adrian Cox
2001-08-20  1:27                         ` Richard B. Johnson
2001-08-20 11:08                           ` Helge Hafting
2001-08-20 11:50                           ` Ian Stirling
2001-08-21 13:55                       ` Andreas Bombe
2001-08-17 20:00                     ` Andreas Dilger
2001-08-07  6:27       ` John Polyakov
2001-08-06 23:28         ` Rob Landley
2001-08-07 10:10           ` Christopher E. Brown
2001-08-07 14:05             ` Joel Jaeggli
2001-08-07  6:41         ` Crutcher Dunnavant
2001-08-07  6:45         ` Ryan Mack
2001-08-07  6:57         ` Evgeny Polyakov
2001-08-07  7:08         ` Evgeny Polyakov
2001-08-07  7:23           ` Sean Hunter
2001-08-07  8:39             ` Ben Ford
2001-08-07 12:28             ` Kevin Krieser
2001-08-07 12:39               ` Richard B. Johnson
2001-08-07 14:21               ` Ignacio Vazquez-Abrams
2001-08-07  7:26           ` Ryan Mack
2001-08-07  7:34           ` Jeffrey Considine
2001-08-07  7:49           ` Crutcher Dunnavant
2001-08-07  9:01           ` Peter Wächtler
2001-08-07 20:09       ` Maciej Zenczykowski
2001-08-07 20:30   ` Ian Stirling
2001-08-07  4:12 ` Steve VanDevender
2001-08-07  7:34   ` Steve VanDevender
2001-08-07  7:55     ` Crutcher Dunnavant
2001-08-07 15:17     ` Garett Spencley
2001-08-07  7:49   ` Helge Hafting
2001-08-07  7:58     ` Crutcher Dunnavant
2001-08-07  9:23       ` Helge Hafting
2001-08-07 13:29         ` Wichert Akkerman
2001-08-07 15:56         ` Chris Wedgwood
2001-08-07 16:54           ` Alan Cox
2001-08-07 17:10             ` Chris Wedgwood
2001-08-07  9:52   ` Brian May
2001-08-07 14:48     ` Joel Jaeggli
2001-08-07 15:59       ` Chris Wedgwood
2001-08-07 16:18         ` Joel Jaeggli
2001-08-07 16:24           ` Florian Weimer
2001-08-08  2:13     ` Dr. Kelsey Hudson
2001-08-07 10:33 ` Andrea Arcangeli

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=m1elq9o8f9.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tegeran@home.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).