From: Haiyang Zhang <haiyangz@microsoft.com>
To: linux-hyperv@vger.kernel.org, akpm@linux-foundation.org,
corbet@lwn.net, linux-mm@kvack.org, linux-doc@vger.kernel.org
Cc: haiyangz@microsoft.com, decui@microsoft.com, kys@microsoft.com,
paulros@microsoft.com, olaf@aepfle.de, vkuznets@redhat.com,
davem@davemloft.net, wei.liu@kernel.org, longli@microsoft.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] docs/mm: Specify page frag size is not bigger than PAGE_SIZE
Date: Thu, 3 Apr 2025 14:21:49 -0700 [thread overview]
Message-ID: <1743715309-318-3-git-send-email-haiyangz@microsoft.com> (raw)
In-Reply-To: <1743715309-318-1-git-send-email-haiyangz@microsoft.com>
The page frag allocator is not designed for fragsz > PAGE_SIZE.
Specify this in the document.
Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
---
Documentation/mm/page_frags.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/mm/page_frags.rst b/Documentation/mm/page_frags.rst
index 503ca6cdb804..212ecc69dd74 100644
--- a/Documentation/mm/page_frags.rst
+++ b/Documentation/mm/page_frags.rst
@@ -2,7 +2,7 @@
Page fragments
==============
-A page fragment is an arbitrary-length arbitrary-offset area of memory
+A page fragment is a len <= PAGE_SIZE, arbitrary-offset area of memory
which resides within a 0 or higher order compound page. Multiple
fragments within that page are individually refcounted, in the page's
reference counter.
--
2.34.1
next prev parent reply other threads:[~2025-04-03 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 21:21 [PATCH 0/2] mm: Explicitly check & doc fragsz limit Haiyang Zhang
2025-04-03 21:21 ` [PATCH 1/2] mm: page_frag: Check fragsz at the beginning of __page_frag_alloc_align() Haiyang Zhang
2025-04-16 7:37 ` Yunsheng Lin
2025-04-16 14:11 ` [EXTERNAL] " Haiyang Zhang
2025-04-03 21:21 ` Haiyang Zhang [this message]
2025-04-15 21:40 ` [PATCH 0/2] mm: Explicitly check & doc fragsz limit Haiyang Zhang
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=1743715309-318-3-git-send-email-haiyangz@microsoft.com \
--to=haiyangz@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longli@microsoft.com \
--cc=olaf@aepfle.de \
--cc=paulros@microsoft.com \
--cc=vkuznets@redhat.com \
--cc=wei.liu@kernel.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;
as well as URLs for NNTP newsgroup(s).