From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: [0/11] hugetlb: series to remove custom inode allocation
Date: Tue, 12 Nov 2002 00:28:53 -0800 [thread overview]
Message-ID: <E18BWPl-0005K4-00@holomorphy> (raw)
This series of patches removes the custom inode allocator from
arch/i386/mm/hugetlbpage.c
It's broken up into 11 incremental steps that progressively reduce
inode dependence, and in the final two stages replace the inode usage
entirely with direct usage of radix trees and refcounting.
The level of testing is very low, but I'd like to release this early.
[1/11] hugetlb: revert doublefreeing patch
[2/11] hugetlb: wrap set_new_inode() with alloc_key()
[3/11] hugetlb: wrap release path with release_key()
[4/11] hugetlb: wrap hugetlb_prefault with prefault_key()
[5/11] hugetlb: embed busy flag in key structure
[6/11] hugetlb: remove direct usage of struct inode
[7/11] hugetlb: substitute hugetlb_key for struct inode
[8/11] hugetlb: reduce inode usage in prefault_key()
[9/11] hugetlb: move inode attributes into hugetlb_key
[10/11] hugetlb: use radix trees instead of inodes
[11/11] hugetlb: add reference counting to hugetlb_keys
Bill
reply other threads:[~2002-11-12 8:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E18BWPl-0005K4-00@holomorphy \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®