Re: [PATCH v3 0/5] Add new system call for non-destructive peek and inspection to posix ipc mqueue

Well, I will see that for reference
Before that here is quick question from my side-
Which better and clean approach

1) Current implementation follows one system call to one msg copy to
user space as per priority and FIFO with a given index value from
posix IPC RB Tree, this allows us  to go beyond Just from peek to
early inspection in some other use case by passing valid index.

2) Just dump everything  and all data in one call to user space.


Thanks,
Mathura


On Tue, 14 Apr 2026 at 05:41, Andrei Vagin <[email protected]> wrote:
>
> On Mon, Apr 13, 2026 at 4:30=E2=80=AFPM Mathura <[email protected]=
om> wrote:
> >
> > Hi, Andrei
> >
> > Thanks for reviewing and time,
> > I saw the code what you pointing to, here is current constraint what I =
see-
>
> That was my mistake. It happens when I am rushing through some
> unfamiliar code. I wasn't aware that IPC queues and POSIX mqueues
> shared some kernel logic. However, I still think it=E2=80=99s worth looki=
ng at the
> MSG_COPY implementation for IPC queues as a reference.
>
> Thanks,
> Andrei