io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Josef <josef.grieb@gmail.com>, io-uring@vger.kernel.org
Cc: norman@apache.org
Subject: Re: SQPOLL question
Date: Mon, 7 Sep 2020 06:49:13 -0600	[thread overview]
Message-ID: <93e9b2a2-b4b4-3cde-b5a7-64c8c504848d@kernel.dk> (raw)
In-Reply-To: <CAAss7+rgZ+9GsMq8rRN11FerWjMRosBgAv=Dokw+5QfBsUE4Uw@mail.gmail.com>

On 9/7/20 4:23 AM, Josef wrote:
>> On top of that, capabilities will also be reduced from root to
>> CAP_SYS_NICE instead, and sharing across rings for the SQPOLL thread
>> will be supported. So it'll be a lot more useful/flexible in general.
> 
> oha that's nice, I'm pretty excited :)
> 
> I'm just wondering if all op are supported when the SQPOLL flag is
> set? the accept op seems to fail with -EINVAL, when I enable SQPOLL
> 
> to reproduce it:
> https://gist.github.com/1Jo1/accb91b737abb55d07487799739ad70a
> (just want to test a non blocking accept op in SQPOLL mode)

Yes, that is known, you cannot open/close descriptors with the
SQPOLL that requires fixed files, as that requires modifying the
file descriptor. 5.10 should not have any limitations.

-- 
Jens Axboe


  reply	other threads:[~2020-09-07 12:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06 15:44 SQPOLL question Josef
2020-09-06 15:49 ` Jens Axboe
2020-09-06 16:24   ` Josef
2020-09-06 16:25     ` Jens Axboe
2020-09-07 10:23       ` Josef
2020-09-07 12:49         ` Jens Axboe [this message]
2020-09-07 14:58           ` Josef
2020-09-07 15:51             ` Jens Axboe
2020-09-08  6:47               ` Josef
2020-09-08 14:36                 ` Jens Axboe
2020-09-08 14:57                   ` Jens Axboe
2020-09-08 17:42                     ` Josef
2020-09-08 17:46                       ` Jens Axboe

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=93e9b2a2-b4b4-3cde-b5a7-64c8c504848d@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=josef.grieb@gmail.com \
    --cc=norman@apache.org \
    /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;
as well as URLs for NNTP newsgroup(s).