From: Eric Wong <e@80x24.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: meta@public-inbox.org, infra@gentoo.org
Subject: Re: public-inbox skipping new inboxes or many mails
Date: Sun, 15 Dec 2024 00:49:53 +0000 [thread overview]
Message-ID: <20241215004953.M337494@dcvr> (raw)
In-Reply-To: <robbat2-20240717T025915-124684207Z@orbis-terrarum.net>
"Robin H. Johnson" <robbat2@gentoo.org> wrote:
> dev-perl/Linux-Inotify2 will be up to date. No guarantees that the
> kernel is up to date - some legacy boxes at sponsors are pretty crufty
> and have been unsafe to reboot to new kernels when we lack any OOB
> management access: to that end, public-inbox's responsiveness is amazing
> even running on a 10+ year old RAID1 HDD spinner setup.
Btw, are the kernels on those machines too old for io_uring?
I've been considering adding st_dev-aware parallelism for
HDDs(*), but I'd imagine an io_uring-capable kernel could be
better than userspace trying to divide tasks based on
(st_dev|mountpoint) since it's possible to have multiple
mountpoints pointing to the same physical device...
Also, would those old machines also benefit from forking to
parallelize the userspace CPU use? I wouldn't mind combining
both io_uring AND forking to take advantage of SMP, of course.
(*) st_dev-aware parallelism works well in my experience with HDDs
in a different project, but I also didn't have multiple
active mountpoints pointing to the same physical device.
prev parent reply other threads:[~2024-12-15 0:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 6:15 public-inbox skipping new inboxes or many mails Robin H. Johnson
2024-07-15 21:03 ` Eric Wong
2024-07-15 21:45 ` Robin H. Johnson
2024-07-15 23:58 ` Eric Wong
2024-07-16 5:45 ` Robin H. Johnson
2024-07-16 19:05 ` Eric Wong
2024-07-17 3:04 ` Robin H. Johnson
2024-07-17 23:25 ` Eric Wong
2024-07-17 23:50 ` Eric Wong
2024-07-18 0:02 ` Robin H. Johnson
2024-12-15 0:49 ` Eric Wong [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241215004953.M337494@dcvr \
--to=e@80x24.org \
--cc=infra@gentoo.org \
--cc=meta@public-inbox.org \
--cc=robbat2@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).