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: Tue, 20 Aug 2013 08:52:17 +0200 [thread overview]
Message-ID: <1376981537.5651.18.camel@pracovni> (raw)
In-Reply-To: <21010.11209.818043.191186@pilspetsen.it.uu.se>
Mikael Pettersson píše v Po 19. 08. 2013 v 16:29 +0200:
> 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
I think I recall that we did that for portability of LARGE FILES (64bit
offsets) at that time (think 10 years ago, various linux distros, MS
Windows, Mac OS, BeOS, various BSD Unices...). Perhaps the situation is
better (file descriptors with 64bit offsets are more portable) now?
Anyway, I have just converted the XHDI to using raw Unix file
descriptors and guess what - there's NO measurable difference (at least
using the previously mentioned XFERRATE.TTP).
Unless someone has a good reason for committing the Unix file
descriptors I'll throw it away and return to good old stdio.
Petr
next prev parent reply other threads:[~2013-08-20 6:52 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 [this message]
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=1376981537.5651.18.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