From: David Hildenbrand <david@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-s390@vger.kernel.org
Subject: Re: Removing page->index
Date: Tue, 10 Dec 2024 13:16:24 +0100 [thread overview]
Message-ID: <1a02554d-d7c1-4925-8180-a39bd6ecdd32@redhat.com> (raw)
In-Reply-To: <20241210130420.534a6512@p-imbrenda>
On 10.12.24 13:04, Claudio Imbrenda wrote:
> On Tue, 10 Dec 2024 12:05:25 +0100
> David Hildenbrand <david@redhat.com> wrote:
>
>> On 09.12.24 18:36, Claudio Imbrenda wrote:
>>> On Wed, 4 Dec 2024 16:58:52 +0100
>>> David Hildenbrand <david@redhat.com> wrote:
>
> [...]
>
>>>> I know that Claudio is working on some changes, but not sure how that
>>>> would affect gmap's usage of page->index.
>>>
>>> After I'm done, we won't use page->index anymore.
>>>
>>> The changes I'm working on are massive, it's very impractical to push
>>> everything at once, so I'm refactoring and splitting smaller and more
>>> manageable (and reviewable) series.
>>>
>>> This means that it will take some time before I'm done (I'm *hoping*
>>> to be done for 6.15)
>>
>> Thanks for the information. So for the time being, we could likely
>> switch to page->private.
>>
>> One question may be whether these (not-user-space) page tables should at
>> some point deserve a dedicated memdesc. But likely the question is what
>
> maybe? but given that everything is changing all the time, I'm avoiding
> any magic logic in struct page / struct folio.
I think Willy wants to get rid of page->index in the next release, so
any way to avoid the page->index usage in s390x is appreciated.
page->private might be the low hanging fruit. If your approach is
feasible in that time frame, it would also be great.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-12-10 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 19:51 Matthew Wilcox
2024-12-04 12:01 ` Thomas Zimmermann
2024-12-04 15:58 ` David Hildenbrand
2024-12-09 17:36 ` Claudio Imbrenda
2024-12-10 11:05 ` David Hildenbrand
2024-12-10 12:04 ` Claudio Imbrenda
2024-12-10 12:16 ` David Hildenbrand [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=1a02554d-d7c1-4925-8180-a39bd6ecdd32@redhat.com \
--to=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imbrenda@linux.ibm.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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