Date: Sat, 13 Jan 2024 21:50:47 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: =?utf-8?B?Vmluw61jaXVz?= dos Santos Oliveira <vini.ipsmaker@gmail.com> Cc: freebsd-threads@freebsd.org Subject: Re: aio_read2() and aio_write2() Message-ID: <ZaLplyztsogCXSEZ@kib.kiev.ua> In-Reply-To: <CAK9RveJfZkESHpQjhO1%2Byn%2BUkvw0Vr5u8fyZBgSh3a8RWqv=bw@mail.gmail.com> References: <CAK9RveK=sUc=xSExehvNwH92uTexjhp0=L63sbw-sfkRFdV4Dg@mail.gmail.com> <ZaF4tWnqhKrNtNBI@kib.kiev.ua> <CAK9RveJfZkESHpQjhO1%2Byn%2BUkvw0Vr5u8fyZBgSh3a8RWqv=bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 12, 2024 at 02:44:11PM -0300, Vinícius dos Santos Oliveira wrote: > Em sex., 12 de jan. de 2024 às 14:37, Konstantin Belousov > <kostikbel@gmail.com> escreveu: > > Do you need a new syscall for this? > > Not really. As long as there's a way to opt-in for ignoring the member > aiocb->aio_offset, it works for me. Please see https://reviews.freebsd.org/D43448; not tested. Effectively I added the new ops to lio_listio(2) instead.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZaLplyztsogCXSEZ>