public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Wei Yang <richard.weiyang@gmail.com>,
	peterz@infradead.org, vbabka@suse.cz, will@kernel.org,
	linyunsheng@huawei.com, aarcange@redhat.com, feng.tang@intel.com,
	ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: remove offset check on page->compound_head and folio->lru
Date: Sat, 8 Jan 2022 08:13:40 +0000	[thread overview]
Message-ID: <20220108081340.3oi2z2rm3cbqozzt@master> (raw)
In-Reply-To: <YdjfsbAR0UlwyC6b@casper.infradead.org>

On Sat, Jan 08, 2022 at 12:49:53AM +0000, Matthew Wilcox wrote:
>On Fri, Jan 07, 2022 at 04:08:25PM -0800, Andrew Morton wrote:
>> On Fri, 7 Jan 2022 22:11:20 +0000 Matthew Wilcox <willy@infradead.org> wrote:
>> 
>> > > Hi, Matthew
>> > > 
>> > > Would you mind sharing some insight on this check?
>> > 
>> > It's right there in the comments.
>> 
>> Well I can't figure out which comment you're referring to?
>
>         * WARNING: bit 0 of the first word is used for PageTail(). That
>         * means the other users of this union MUST NOT use the bit to
>         * avoid collision and false-positive PageTail().
>

I know this requirement on bit 0 of first word. But I don't see the connection
between this and the check of page->compound_head and folio->lru.

This is more like a internal requirement on struct page. There are 8 struct in
this five words union. And this requirement apply to bit 0 of first word of
all those five struct.

To me, if folio has the same layout of page, folio meets this requirement. I
still not catch the point why we need this check here.

-- 
Wei Yang
Help you, Help me

  parent reply	other threads:[~2022-01-08  8:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 23:52 [PATCH] mm: remove offset check on page->compound_head and folio->lru Wei Yang
2022-01-07  3:59 ` Matthew Wilcox
2022-01-07 13:40   ` Wei Yang
2022-01-07 22:11     ` Matthew Wilcox
2022-01-08  0:08       ` Andrew Morton
2022-01-08  0:49         ` Matthew Wilcox
2022-01-08  2:41           ` Andrew Morton
2022-01-08  8:13           ` Wei Yang [this message]
2022-01-23  1:38             ` Wei Yang
2022-01-24 10:30               ` Vlastimil Babka
2022-01-24 22:55                 ` Wei Yang
2022-01-25 10:11                   ` Vlastimil Babka
2022-01-27  1:10                     ` Wei Yang
2022-01-27 15:42                       ` Vlastimil Babka
2022-01-29  0:47                         ` Wei Yang
2022-02-24  1:03                 ` Wei Yang
2022-02-17  0:34           ` Wei Yang
2022-01-08  0:27       ` Wei Yang

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=20220108081340.3oi2z2rm3cbqozzt@master \
    --to=richard.weiyang@gmail.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=peterz@infradead.org \
    --cc=vbabka@suse.cz \
    --cc=will@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