From: Petr Stehlik <pstehlik@sophics.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>, aranym@lists.bobek.cz
Subject: Re: nfhd performance
Date: Tue, 20 Aug 2013 08:24:58 +0200 [thread overview]
Message-ID: <1376979898.5651.10.camel@pracovni> (raw)
In-Reply-To: <CAMuHMdUwzzx5Ae7sdvbRBtgY4UoXpo5-ig4PfdqFH4beWv_AHQ@mail.gmail.com>
Geert Uytterhoeven píše v Pá 16. 08. 2013 v 23:57 +0200:
> In a kernel that has both IDE and nfhd support, once everything is in the
> buffer cache, I get:
>
> atari:~# dd if=/dev/hda2 bs=1M of=/dev/null
> 141114880 bytes (141 MB) copied, 5.91 seconds, 23.9 MB/s
> atari:~# dd if=/dev/nfhd8p2 bs=1M of=/dev/null
> 141114880 bytes (141 MB) copied, 17.09 seconds, 8.3 MB/s
FYI, I have just tried running XFERRATE.TTP (freeware by
AnodyneSoftware.com) under plain TOS with clock driven by RTC and disk
image without byteswap (it's still my original 1000 MB disk from Atari
Falcon). I got the following results with a small 30 MB partition that
most probably fully fit into host buffer cache:
Rwabs() transfer rate: 26660-26220 kb/sec
XHDI transfer rate: 26750 kb/sec
Please note that the Rwabs is a direct BIOS access. I think it's rather
close if not equivalent to your 'dd if=/dev/hda2'.
It basically means that since the XHDI path is slightly shorter code
path so the data transfer is very slightly faster. That's actually what
one could expect.
I will try more tests, especially with ByteSwap in ARAnyM enabled (to
see if there's a performance penalty). Will also try changing fread to
read and implement reading more sectors at once in the XHDI NatFeat
implementation. Will post my results here.
In summary, the slow nfhd above seems to be caused by the linux-m68k
implementation as I can't see such slow down under plain TOS.
Petr
prev parent reply other threads:[~2013-08-20 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 21:57 nfhd performance Geert Uytterhoeven
2013-08-17 2:01 ` Michael Schmitz
2013-08-17 7:36 ` Geert Uytterhoeven
2013-08-19 14:29 ` Mikael Pettersson
2013-08-19 15:48 ` Petr Stehlik
2013-08-20 6:52 ` Petr Stehlik
2013-08-18 5:08 ` Petr Stehlik
2013-08-20 6:24 ` Petr Stehlik [this message]
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=1376979898.5651.10.camel@pracovni \
--to=pstehlik@sophics.cz \
--cc=aranym@lists.bobek.cz \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
/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