From: Petr Stehlik <pstehlik@sophics.cz>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>,
Linux/m68k <linux-m68k@vger.kernel.org>,
aranym@lists.bobek.cz
Subject: Re: nfhd performance
Date: Mon, 19 Aug 2013 17:48:24 +0200 [thread overview]
Message-ID: <1376927304.17125.19.camel@pracovni> (raw)
In-Reply-To: <21010.11209.818043.191186@pilspetsen.it.uu.se>
> Part of the problem is that ByteSwap = No setting. Contrary to what one might
> think, "No" there actually means "yes, byteswap every sector read or written".
>
> Grep for byteswap in aranym's src/natfeat/xhdi.cpp if you don't believe me...
>
> As far as I can tell, this setting is only meaningful if you have an image which
> must be shared with actual HW, and you don't want to byteswap it when migrating
> it between these two roles (HW or aranym). I don't have that requirement, so I
> run my aranym VMs with ByteSwap = Yes, which eliminates that overhead.
Very true.
> There are also other things in xhdi.cpp I don't really like, such as going through
> stdio when raw Unix file-descriptors would do, and the small I/O unit size.
Please suggest a better yet portable way. I've been thinking about
reading more than a single sector at once, that could help a bit. Should
write a benchmark for it first, it seems.
Petr
next prev parent reply other threads:[~2013-08-19 15:48 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 [this message]
2013-08-20 6:52 ` Petr Stehlik
2013-08-18 5:08 ` Petr Stehlik
2013-08-20 6:24 ` Petr Stehlik
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=1376927304.17125.19.camel@pracovni \
--to=pstehlik@sophics.cz \
--cc=aranym@lists.bobek.cz \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=schmitz@biophys.uni-duesseldorf.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