From: Alejandro Colomar <alx@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: linux-man@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
Rik van Riel <riel@surriel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH v4 1/2] man/man2/mremap.2: describe multiple mapping move
Date: Mon, 11 Aug 2025 11:20:05 +0200 [thread overview]
Message-ID: <iny6ro5f37vcthqwscklqx73jscahodilug5d6umleyzq6a67k@ecoey5ud3aer> (raw)
In-Reply-To: <664b00e3-69a0-498a-a7dd-a3d294c0c188@lucifer.local>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
Hi Lorenzo,
On Mon, Aug 11, 2025 at 06:30:38AM +0100, Lorenzo Stoakes wrote:
> > > +Mappings can also simply be moved
> > > +(without any resizing)
> > > +by specifying equal
> > > +.I old_size
> > > +and
> > > +.I new_size
> > > +and using the
> > > +.B MREMAP_FIXED
> > > +flag
> > > +(see below).
> > > +Since Linux 6.17,
> > > +while
> > > +.I old_address
> > > +must reside within a mapping,
> >
> > I don't understand this. What does it mean that old_address must reside
> > within a mapping? It's a point, not a size, so I'm not sure I
> > understand it.
>
> I think if it were a size it would be more confusing no?
>
> It's an address, the address must be located within an existing memory mapping.
What I don't understand is: how could you not comply with that? Could
you pass some old_address that is in two mappings? Being a single
address, that would be impossible, right?
> Will replace with 'located' for clarity.
>
> >
> > > +.I old_size
> > > +may span multiple mappings
> > > +which do not have to be
> > > +adjacent to one another when
> > > +performing a move like this.
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-08-11 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 17:31 [PATCH v4 0/2] man/man2/mremap.2: describe multiple mapping move, shrink Lorenzo Stoakes
2025-08-05 17:31 ` [PATCH v4 1/2] man/man2/mremap.2: describe multiple mapping move Lorenzo Stoakes
2025-08-09 14:25 ` Alejandro Colomar
2025-08-11 5:30 ` Lorenzo Stoakes
2025-08-11 9:20 ` Alejandro Colomar [this message]
2025-08-11 9:25 ` Lorenzo Stoakes
2025-08-11 9:37 ` Alejandro Colomar
2025-08-05 17:31 ` [PATCH v4 2/2] man/man2/mremap.2: describe previously undocumented shrink behaviour Lorenzo Stoakes
2025-08-09 14:33 ` Alejandro Colomar
2025-08-11 5:31 ` Lorenzo Stoakes
2025-08-11 9:20 ` Alejandro Colomar
2025-08-08 13:15 ` [PATCH v4 0/2] man/man2/mremap.2: describe multiple mapping move, shrink Lorenzo Stoakes
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=iny6ro5f37vcthqwscklqx73jscahodilug5d6umleyzq6a67k@ecoey5ud3aer \
--to=alx@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=peterx@redhat.com \
--cc=pfalcato@suse.de \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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