public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Matthew Wilcox <willy@infradead.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-s390@vger.kernel.org
Subject: Re: Removing page->index
Date: Wed, 4 Dec 2024 13:01:46 +0100	[thread overview]
Message-ID: <bfc97a69-de69-45ec-875d-2f1e652e0f94@suse.de> (raw)
In-Reply-To: <Z09hOy-UY9KC8WMb@casper.infradead.org>

Hi


Am 03.12.24 um 20:51 schrieb Matthew Wilcox:
> I've pushed out a new tree to
> git://git.infradead.org/users/willy/pagecache.git shrunk-page
> aka
> http://git.infradead.org/?p=users/willy/pagecache.git;a=shortlog;h=refs/heads/shrunk-page
>
> The observant will notice that it doesn't actually shrink struct page
> yet.  However, we're getting close.  What it does do is rename
> page->index to page->__folio_index to prevent new users of page->index
> from showing up.
>
> There are (I believe) three build failures in that tree:
>
>   - fb_defio

It's only used for helpers of the mm code. So it should be good to change.

>   - fbtft

And this reference should be removed IMHO. The driver's display-update 
code has no business in looking at struct page.

Best regards
Thomas

>   - s390's gmap (and vsie?  is that the same thing?)
>
> Other than that, allmodconfig builds on x86 and I'm convinced the build
> bots will tell me about anything else I missed.
>
> Lorenzo is working on fb_defio and fbtft will come along for the ride
> (it's a debug printk, so could just be deleted).
>
> s390 is complicated.  I'd really appreciate some help.
>
> The next step is to feed most of the patches through the appropriate
> subsystems.  Some have already gone into various maintainer trees
> (thanks!)
>
>
> There are still many more steps to go after this; eliminating memcg_data
> is closest to complete, and after that will come (in some order)
> eliminating ->lru, ->mapping, ->refcount and ->mapcount.  We also need
> to move page_pool out into its own structure.

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)


  reply	other threads:[~2024-12-04 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 19:51 Removing page->index Matthew Wilcox
2024-12-04 12:01 ` Thomas Zimmermann [this message]
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

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=bfc97a69-de69-45ec-875d-2f1e652e0f94@suse.de \
    --to=tzimmermann@suse.de \
    --cc=dri-devel@lists.freedesktop.org \
    --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