From: Jens Axboe <[email protected]>
To: Mark Papadakis <[email protected]>
Cc: io-uring <[email protected]>
Subject: Re: Extending the functionality of some SQE OPs
Date: Tue, 21 Jan 2020 13:55:25 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/21/20 1:54 PM, Mark Papadakis wrote:
>
>
> This sounds great. It may wind up being far more useful or important
> down the road, and if this doesn’t bloat the CQE, that’s fantastic.
It's there if we want to use it. And we cannot bloat the CQE otherwise,
the size is fixed. But we can use those 32-bits that are currently not
used.
--
Jens Axboe
prev parent reply other threads:[~2020-01-21 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 7:50 Extending the functionality of some SQE OPs Mark Papadakis
2020-01-21 19:55 ` Jens Axboe
2020-01-21 20:54 ` Mark Papadakis
2020-01-21 20:55 ` Jens Axboe [this message]
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 \
[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