From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2] mm/pdx: Add comments throughout the codebase for pdx
Date: Mon, 10 Jul 2023 17:12:31 +0100 [thread overview]
Message-ID: <64ac2df2.170a0220.87102.74de@mx.google.com> (raw)
In-Reply-To: <03e5e1a7-2c04-c991-e3b7-cea6916ec59b@suse.com>
On Mon, Jul 10, 2023 at 09:43:34AM +0200, Jan Beulich wrote:
> This is ...
> >>> [snip]
> >>> + * This is where compression becomes useful. The idea is to note that if
> >>> + * you have several big chunks of memory sufficiently far apart you can
> >>> + * ignore the middle part of the address because it will always contain
> >>> + * zeroes as long as the base address is sufficiently well aligned and the
> >>> + * length of the region is much smaller than the base address.
> >>
> >> As per above alignment of the base address doesn't really matter.
> > Where above?
>
> ... what "above" here meant.
>
> > As far as I understand you need enough alignment to cover the
> > hole or you won't have zeroes to compress. Point in case:
> >
> > * region1: [0x0000000000000000 -
> > 0x00000000FFFFFFFF]
> >
> > * region2: [0x0001FFFFFFFFF000 -
> > 0x00020000FFFFFFFF]
> >
> > I can agree this configuration is beyond dumb and statistically unlikely to
> > exist in the wild, but it should (IMO) still be covered by that comment.
>
> Right, but this isn't relevant here - in such a case no compression
> can occur, yes, but not (just) because of missing alignment. See the
> example I gave above (in the earlier reply) for where alignment
> clearly doesn't matter for compression to be possible.
>
> Jan
Fair enough. Then I think we can simply drop the last sentence and be done
with it.
So the paragraph becomes:
```
* This is where compression becomes useful. The idea is to note that if
* you have several big chunks of memory sufficiently far apart you can
* ignore the middle part of the address because it will always contain
* zeroes.
```
The details on when or how compression is possible are implicit in the
following example anyway.
Would that, combined with v3, take care of everything? If not, I'll just
merge further patches with the pdx series I have on hold and send
everything together.
Thanks,
Alejandro
next prev parent reply other threads:[~2023-07-10 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 14:02 [PATCH v2] mm/pdx: Add comments throughout the codebase for pdx Alejandro Vallejo
2023-07-06 9:50 ` Jan Beulich
2023-07-07 15:55 ` Alejandro Vallejo
2023-07-10 7:43 ` Jan Beulich
2023-07-10 16:12 ` Alejandro Vallejo [this message]
2023-07-10 16:32 ` Jan Beulich
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=64ac2df2.170a0220.87102.74de@mx.google.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.