From: Finn Thain <fthain@linux-m68k.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Guenter Roeck <linux@roeck-us.net>,
io-uring@vger.kernel.org,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH 03/14] io_uring: specify freeptr usage for SLAB_TYPESAFE_BY_RCU io_kiocb cache
Date: Fri, 22 Nov 2024 10:04:20 +1100 (AEDT) [thread overview]
Message-ID: <19a859ee-a2f8-231b-121b-bcd6df3f7ae5@linux-m68k.org> (raw)
In-Reply-To: <5a7528c4-4391-4bd9-bbdb-a0247f3c76a9@kernel.dk>
On Tue, 19 Nov 2024, Jens Axboe wrote:
> On 11/19/24 10:49 AM, Geert Uytterhoeven wrote:
>
> >
> > The minimum alignment for multi-byte integral values on m68k is 2
> > bytes.
> >
> > See also the comment at
> > https://elixir.bootlin.com/linux/v6.12/source/include/linux/maple_tree.h#L46
>
> Maybe it's time we put m68k to bed? :-)
>
When Linux ceases to implement Unix, it may well lose its relevance to
systems which were designed to run Unix. That hasn't happened yet, AFAIK.
If the legacy Unix ABI were to be replaced, would it need syscalls at all?
Could io_uring offer a better alternative, for a hypothetical new ABI?
prev parent reply other threads:[~2024-11-21 23:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241029152249.667290-1-axboe@kernel.dk>
[not found] ` <20241029152249.667290-4-axboe@kernel.dk>
[not found] ` <37c588d4-2c32-4aad-a19e-642961f200d7@roeck-us.net>
[not found] ` <d4e5a858-1333-4427-a470-350c45b78733@kernel.dk>
2024-11-19 16:21 ` [PATCH 03/14] io_uring: specify freeptr usage for SLAB_TYPESAFE_BY_RCU io_kiocb cache Guenter Roeck
2024-11-19 17:49 ` Geert Uytterhoeven
2024-11-19 19:00 ` Jens Axboe
2024-11-19 19:02 ` Geert Uytterhoeven
2024-11-19 19:10 ` Jens Axboe
2024-11-19 19:25 ` Geert Uytterhoeven
2024-11-19 19:30 ` Jens Axboe
2024-11-19 19:41 ` Geert Uytterhoeven
2024-11-19 19:44 ` Jens Axboe
2024-11-19 19:49 ` Jens Axboe
2024-11-19 21:46 ` Guenter Roeck
2024-11-19 22:30 ` Jens Axboe
2024-11-20 0:08 ` Guenter Roeck
2024-11-20 1:58 ` Jens Axboe
2024-11-20 8:19 ` Geert Uytterhoeven
2024-11-20 8:47 ` Vlastimil Babka
2024-11-20 9:07 ` Geert Uytterhoeven
2024-11-20 9:37 ` Vlastimil Babka
2024-11-20 12:48 ` Geert Uytterhoeven
2024-11-21 23:04 ` Finn Thain [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=19a859ee-a2f8-231b-121b-bcd6df3f7ae5@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=axboe@kernel.dk \
--cc=geert@linux-m68k.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@roeck-us.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