From: Alejandro Colomar <alx.manpages@gmail.com>
To: Zach O'Keefe <zokeefe@google.com>
Cc: Yang Shi <shy828301@gmail.com>,
linux-mm@kvack.org, linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH man-pages v4] madvise.2: add documentation for MADV_COLLAPSE
Date: Tue, 1 Nov 2022 12:38:20 +0100 [thread overview]
Message-ID: <78113c25-a635-8d35-a5db-9657f8adf4a6@gmail.com> (raw)
In-Reply-To: <CAAa6QmQN1u5ynyE7Lce9xEKwRQpG6OU8ZOcgFk5nc1h-AN4YgQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1337 bytes --]
Hey Zach,
On 11/1/22 01:38, Zach O'Keefe wrote:
>>
>> I don't understand this last paragraph (since "Also note ..."). Could you
>> please reword it a little bit?
>>
>
> Sure - I can see that it's hard to parse.
>
> Further up I note that, "If collapse of a given huge
> page-aligned/sized region fails, the operation may continue to attempt
> collapsing the remainder of the specified memory."
>
> Then perhaps it's enough to just state, "In the event multiple
> hugepage-aligned/sized areas fail to collapse, only the most
> recently-failed code will be set in errno"
I like this.
>
> The idea here being: errno only communicates the reason for 1/N
> failures that might have occured.
>
> However -- on second thought -- perhaps this isn't particularly
> useful, as it's already implied. So, my new suggestion would be that
> we should drop it. What do you think?
errno usually behaves like that if you call consecutive calls, but it's not so
obvious how a single call will behave: it could report the last one as in this
case, or the first one since it's the one that made it break. I'd keep it.
[...]
>> Diff for changing a few line breaks (and removing the spurious file):
>>
>
> Thank you so much for this! :)
:)
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-01 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 22:55 Zach OKeefe
2022-10-31 23:36 ` Alejandro Colomar
2022-11-01 0:38 ` Zach O'Keefe
2022-11-01 11:38 ` Alejandro Colomar [this message]
2022-11-01 15:04 ` Zach O'Keefe
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=78113c25-a635-8d35-a5db-9657f8adf4a6@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=shy828301@gmail.com \
--cc=zokeefe@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