linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>,
	linux-mm@kvack.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/2] s390: Remove uses of page->index
Date: Thu, 19 Dec 2024 17:56:54 +0100	[thread overview]
Message-ID: <5fae8eb9-0639-4b1b-aeac-c5adc4172446@redhat.com> (raw)
In-Reply-To: <Z2RPNBDbWvZ9Vu9D@casper.infradead.org>

On 19.12.24 17:52, Matthew Wilcox wrote:
> On Thu, Dec 19, 2024 at 05:33:32PM +0100, David Hildenbrand wrote:
>> On 19.12.24 17:22, Matthew Wilcox (Oracle) wrote:
>>> These two patches compile ... I can promise nothing more than that.
>>>
>>> David suggested to me that the gmap code really should be using ptdesc,
>>> and I think I agree with him.  The vsie code looks quite different
>>> and probably shouldn't be using a ptdesc, but we can use page->private
>>> instead of page->index.  It's not yet clear to me if we'll ever manage
>>> to get rid of page->private.
>>
>> Just curious, does that mean that memdesc would always contain these
>> additional 8 bytes?
> 
> Eventually we'll have a choice to make.
> 
> 1. Shrink struct page to 8 bytes, but we'll need to allocate a 32 byte
>     memdesc for all the current users of page->private
> 2. Shrink struct page to 16 bytes
> 
> I genuinely don't know which will be better for the whole system.
> 
> If you're asking because we can defer some of the mapcount
> work by using the 8 bytes of page->private to store mapcount, then
> yes, let's do that.

Yeah, it could give us a bit more time, until we know that we can just 
get rid of it in all kernel configs. But let's see if that is still a 
problem when we're getting closer to removing them.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-12-19 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 16:22 Matthew Wilcox (Oracle)
2024-12-19 16:22 ` [PATCH 1/2] s390: Convert gmap code to use ptdesc Matthew Wilcox (Oracle)
2024-12-19 21:23   ` Matthew Wilcox
2024-12-20  9:22     ` David Hildenbrand
2024-12-19 16:22 ` [PATCH 2/2] s390: Convert vsie code to use page->private Matthew Wilcox (Oracle)
2024-12-20  9:55   ` David Hildenbrand
2024-12-20 11:40     ` Claudio Imbrenda
2024-12-19 16:33 ` [PATCH 0/2] s390: Remove uses of page->index David Hildenbrand
2024-12-19 16:52   ` Matthew Wilcox
2024-12-19 16:56     ` David Hildenbrand [this message]
2025-01-03 14:53 ` Claudio Imbrenda
2025-01-07 10:23   ` David Hildenbrand

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=5fae8eb9-0639-4b1b-aeac-c5adc4172446@redhat.com \
    --to=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox