From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
patches@lists.linux.dev, Joerg Roedel <joro@8bytes.org>
Subject: [GIT PULL] slab for 5.17 - part 2
Date: Mon, 17 Jan 2022 16:33:02 +0100 [thread overview]
Message-ID: <06e9cd6c-320c-af1a-ef12-55e2e8c13f17@suse.cz> (raw)
Linus,
please pull the remaining slab changes from
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-5.17-part2
======================================
- Finish the conversion to struct slab by removing slab-specific fields
from struct page.
======================================
The previous pull request [1] did most of the conversion, but there was also
series in iommu tree removing the iommu's usage of struct page 'freelist'
field, blocking the final struct page cleanup. So this pull request is based on
the previous one, adds a merge of iommu tree and a single commit on top, and
has been like this in linux-next since Wed last week. The iommu tree went
mainline since then, so this should add just the single commit to mainline now.
Vlastimil
[1] https://lore.kernel.org/all/fa6573eb-9d5c-ef49-06b1-157c16efb868@suse.cz/
Matthew Wilcox (Oracle) (1):
mm: Remove slab from struct page
Vlastimil Babka (1):
Merge branch 'core' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu into slab-struct_slab-part2-v1
drivers/iommu/amd/io_pgtable.c | 110 ++++++--------
drivers/iommu/dma-iommu.c | 274 +++++++++++++++++++++++++++--------
drivers/iommu/intel/iommu.c | 89 ++++--------
drivers/iommu/io-pgtable-arm.c | 9 +-
drivers/iommu/iommu.c | 3 +-
drivers/iommu/iova.c | 209 ++------------------------
drivers/vdpa/vdpa_user/iova_domain.c | 8 -
include/linux/iommu.h | 3 +-
include/linux/iova.h | 68 +--------
include/linux/mm_types.h | 28 ----
include/linux/page-flags.h | 37 -----
include/trace/events/iommu.h | 10 +-
mm/slab.h | 6 -
13 files changed, 314 insertions(+), 540 deletions(-)
next reply other threads:[~2022-01-17 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 15:33 Vlastimil Babka [this message]
2022-01-18 4:53 ` pr-tracker-bot
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=06e9cd6c-320c-af1a-ef12-55e2e8c13f17@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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