From: "Alyssa M via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] openat()
Date: Sat, 6 Apr 2024 21:36:49 -0400 [thread overview]
Message-ID: <17124538090.BD80ABf5D.12467@composer.9fans.topicbox.com> (raw)
In-Reply-To: <17124367090.cDf02.77195@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Well I got curious, and wrote a test program for my Linux RPi:
Doing the equivalent of what du(1) does (a recursive tree walk statting every file) seemed to be about 15% faster with openat/fstatat than with open/lstat. This was on a local drive (SD card).
Over 9p to my Plan 9 RPi from Linux it appeared to make no measurable difference at all (though I don't know whether v9fs can take advantage of the *at capability).
Maybe there's some use case where it makes a more dramatic difference. My tests were not very scientific.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T675e737e776e5a9c-M5f33ea51d2130dafe5918a21
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1299 bytes --]
next prev parent reply other threads:[~2024-04-07 1:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 19:50 ron minnich
2024-04-05 20:12 ` Gorka Guardiola
2024-04-05 20:15 ` Gorka Guardiola
2024-04-05 20:36 ` Gorka Guardiola
2024-04-05 21:22 ` ron minnich
2024-04-05 21:43 ` Bakul Shah via 9fans
2024-04-05 21:49 ` Alyssa M via 9fans
2024-04-05 22:29 ` Gorka Guardiola
2024-04-06 3:18 ` moody
2024-04-06 17:35 ` ron minnich
2024-04-06 19:23 ` David Leimbach via 9fans
2024-04-06 19:54 ` Bakul Shah via 9fans
2024-04-06 19:24 ` Alyssa M via 9fans
2024-04-06 20:51 ` moody
2024-04-07 1:36 ` Alyssa M via 9fans [this message]
2024-04-07 15:00 ` Alyssa M via 9fans
2024-04-10 12:17 ` wb.kloke
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=17124538090.BD80ABf5D.12467@composer.9fans.topicbox.com \
--to=9fans@9fans.net \
/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).