public inbox for [email protected]
 help / color / mirror / Atom feed
From: Stefano Garzarella <[email protected]>
To: Jens Axboe <[email protected]>, Pavel Begunkov <[email protected]>
Cc: [email protected], [email protected]
Subject: Are CAP_SYS_ADMIN and CAP_SYS_NICE still needed for SQPOLL?
Date: Thu, 25 Mar 2021 12:33:22 +0100	[thread overview]
Message-ID: <20210325113322.ecnji3xejozqdpwt@steredhat> (raw)

Hi Jens, Hi Pavel,
I was taking a look at the new SQPOLL handling with io_thread instead of 
kthread. Great job! Really nice feature that maybe can be reused also in 
other scenarios (e.g. vhost).

Regarding SQPOLL, IIUC these new threads are much closer to user 
threads, so is there still a need to require CAP_SYS_ADMIN and 
CAP_SYS_NICE to enable SQPOLL?

Thanks,
Stefano


             reply	other threads:[~2021-03-25 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 11:33 Stefano Garzarella [this message]
2021-03-25 13:44 ` Are CAP_SYS_ADMIN and CAP_SYS_NICE still needed for SQPOLL? Pavel Begunkov
2021-03-25 14:02   ` Jens Axboe
2021-03-25 14:09     ` Stefano Garzarella

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=20210325113322.ecnji3xejozqdpwt@steredhat \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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