From: Alejandro Colomar <alx@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: aarcange@redhat.com, lorenzo.stoakes@oracle.com,
david@redhat.com, peterx@redhat.com, lokeshgidra@google.com,
linux-man@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/1] man/man2/ioctl_userfaultfd.2, UFFDIO_MOVE.2const: Add UFFDIO_MOVE page
Date: Wed, 23 Apr 2025 23:10:15 +0200 [thread overview]
Message-ID: <2uffhjsbzq2hmgx5o5ac6u6ifi25nxhqy75irf7atjd6shctwg@eo7whozxpmqb> (raw)
In-Reply-To: <CAJuCfpGdMZE=oazv4yEPGsmJAt8rL3yNHBs-mkGXD1Mfh8gNLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
Hi Suren,
On Wed, Apr 23, 2025 at 12:55:41PM -0700, Suren Baghdasaryan wrote:
> > > > +.B struct uffdio_move {
> > > > +.BR " __u64 dst;" " /* Destination of move */"
> > > > +.BR " __u64 src;" " /* Source of move */"
> > > > +.BR " __u64 len;" " /* Number of bytes to move */"
> > >
> > > Are we in time to name this size instead of len? Length usually refers
> > > to the number of non-zero characters in a string, while size refers to
> > > number of bytes in some object, which is more appropriate in these
> > > cases.
> > >
> > > If this has already been released in the kernel, don't worry about it,
> > > but if it hasn't, maybe we should call it size?
>
> Sorry, it was released back in 6.8.
Okay, no problem.
> > > > +.P
> > > > +The following value may be bitwise ORed in
> > > > +.I mode
> > >
> > > Please use .mode instead of mode. That makes it more obvious that we're
> > > talking about a struct member. I know most pages don't do this, but I'm
> > > planning a global change for consistency soon; since this page is new,
> > > we can start clean and do it as
> > >
> > > .I .mode
> > >
> > > This is done in a few cases already in fanotify(7), for example.
>
> Ack. I assume that should be done everywhere else.
Yep.
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-04-23 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 1:12 Suren Baghdasaryan
2025-04-23 8:16 ` Alejandro Colomar
2025-04-23 17:15 ` Suren Baghdasaryan
2025-04-23 19:55 ` Suren Baghdasaryan
2025-04-23 21:10 ` Alejandro Colomar [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 \
--in-reply-to=2uffhjsbzq2hmgx5o5ac6u6ifi25nxhqy75irf7atjd6shctwg@eo7whozxpmqb \
--to=alx@kernel.org \
--cc=aarcange@redhat.com \
--cc=david@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=peterx@redhat.com \
--cc=surenb@google.com \
/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