[GIT PULL] man/io_uring: Small fixes and additions

[CPestka]

This:

1. Fixes a couple of fmt things
2. Updates the sqe struct
3. Moves the read op as an example of an sqe to the bullet point where sqes are described first
4. Adds a remark that the generally described order of operation in the beginning of the man page can significantly change based on config parameters and usage

5. Adds a pointer to where one can find info about memory models after the statement that, while they are important here, they are out of scope for the man page

   git request-pull output:

   
   The following changes since commit 206650ff72b6ea4d76921f9c91ebfffd9902e6a0:
   
   test/fixed-hugepage: skip test on -ENOMEM (2024-09-27 10:27:10 -0600)

are available in the Git repository at:

https://github.com/CPestka/liburing io_uring_man

for you to fetch changes up to 8a7810d0ac44fcb3082ece0f9d699414d8d590b3:

man/io_uring: Add remark about where to find info about memory ordering (2024-09-28 14:36:19 +0200)

---

CPestka (5): man/io_uring: Formatting fixes man/io_uring: Moved SQE example of a read request to SQE description man/io_uring: Add remark that operational behavior changes with flags man/io_uring: Update SQE struct man/io_uring: Add remark about where to find info about memory ordering

man/io_uring.7 | 169 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------

----
<details>
<summary>Click to show/hide pull request guidelines</summary>

## Pull Request Guidelines
1. To make everyone easily filter pull request from the email
notification, use `[GIT PULL]` as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

7. Follow the commit message format rules below.
8. Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

### Commit message format rules:
1. The first line is title (don't be more than 72 chars if possible).
2. Then an empty line.
3. Then a description (may be omitted for truly trivial changes).
9. Then an empty line again (if it has a description).
10. Then a `Signed-off-by` tag with your real name and email. For example:

Signed-off-by: Foo Bar foo.bar@gmail.com

The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).

Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.

Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.

If the commit is a fix for an issue, add a `Fixes` tag with the issue
URL.

Don't use GitHub anonymous email like this as the commit author:

123456789+username@users.noreply.github.com

Use a real email address!

### Commit message example:

src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the syscall instead of by posting an internal timeout. This was done to be both more efficient, but also to enable multi-threaded use the wait side. If we touch the SQ state by flushing it, that isn't safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402 Signed-off-by: Jens Axboe axboe@kernel.dk

</details>

----
## By submitting this pull request, I acknowledge that:
1. I have followed the above pull request guidelines.
2. I have the rights to submit this work under the same license.
3. I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).