All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Mathura <academic1mathura@gmail.com>
Cc: criu@lists.linux.dev, avagin@gmail.com
Subject: Re: [PATCH v3 1/4] IPC: Added two new system call mq_recvmmsg() and mq_sendmmsg()
Date: Fri, 12 Jun 2026 15:52:14 +0200	[thread overview]
Message-ID: <c6bcebf4-670f-48c0-ae20-686bfd6e087f@virtuozzo.com> (raw)
In-Reply-To: <CA+QNo227VE0j0eNxDwxYQz1GReq3fXmOxgM_PJ7rX7LBDQTCow@mail.gmail.com>



On 6/12/26 14:35, Mathura wrote:
> Hi,
> 
> I am resending this due to a mail server error.

Sorry, I accidentally replied with html and broke the formating.

> 
> I never tested in compat mode. I will do and look at all the points
> mentioned above.
> I will insist you to please do a complete review and kindly tell me if
> any more such or any architecture specific issue exists.
> 
> Regarding optimization on target retrieval from tree, can you provide
> any suggestion how we can minimize complete traversal required for
> each time. if we maintain state how we know the current cache or
> stored efficient node belongs to which system calls from userspace if
> we assume many concurrent processes calling it.

My idea was to basically just have `struct rb_node **last = NULL;`
in do_mq_recvmmsg() and pass it down to mq_peek_index(), so that we can
start the walk from last instead of rb_last, just doing `node = rb_prev(last)`
instead of full tree walk. You should set node back to last after that.
Only thing we should be careful about is that info->msg_tree
should be sufficiently locked to avoid removal of last from the tree.

> 
> Thanks,
> Mathura

-- 
Best regards, Pavel Tikhomirov
Senior Software Developer, Virtuozzo.


  reply	other threads:[~2026-06-12 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12  5:20 [PATCH v3 0/4] Add two new system call mq_recvmmsg() and mq_sendmmsg() to posix ipc mqueue Mathura_Kumar
2026-06-12  5:20 ` [PATCH v3 1/4] IPC: Added two new system call mq_recvmmsg() and mq_sendmmsg() Mathura_Kumar
2026-06-12 11:49   ` Pavel Tikhomirov
     [not found]     ` <CA+QNo20DfeHOVYq4XgyCaUU4-3AYxh+tDyymjCD1DLkw7zytrA@mail.gmail.com>
2026-06-12 12:35       ` Mathura
2026-06-12 13:52         ` Pavel Tikhomirov [this message]
2026-06-14 14:37           ` Mathura
2026-06-12  5:20 ` [PATCH v3 2/4] IPC: Added system call entry in all of most common architectures Mathura_Kumar
2026-06-12  5:20 ` [PATCH v3 3/4] IPC: Added system call entry in performance tool Mathura_Kumar
2026-06-12  5:20 ` [PATCH v3 4/4] Test: Added self-testing and documentation Mathura_Kumar
  -- strict thread matches above, loose matches on Subject: below --
2026-06-20 11:23 [PATCH v3 0/4] Add two new system call mq_recvmmsg() and mq_sendmmsg() to posix ipc mqueue Mathura_Kumar
2026-06-20 11:23 ` [PATCH v3 1/4] IPC: Added two new system call mq_recvmmsg() and mq_sendmmsg() Mathura_Kumar
2026-06-20 20:29   ` Andrei Vagin
2026-06-20 22:36 [PATCH v3 0/4] Add two new system call mq_recvmmsg() and mq_sendmmsg() to posix ipc mqueue Mathura_Kumar
2026-06-20 22:36 ` [PATCH v3 1/4] IPC: Added two new system call mq_recvmmsg() and mq_sendmmsg() Mathura_Kumar
2026-08-16 15:34 [PATCH v3 0/4] Add two new system call mq_recvmmsg() and mq_sendmmsg() to posix ipc mqueue mathura kumar
2026-08-16 15:34 ` [PATCH v3 1/4] IPC: Added two new system call mq_recvmmsg() and mq_sendmmsg() mathura kumar

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=c6bcebf4-670f-48c0-ae20-686bfd6e087f@virtuozzo.com \
    --to=ptikhomirov@virtuozzo.com \
    --cc=academic1mathura@gmail.com \
    --cc=avagin@gmail.com \
    --cc=criu@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.