Linux-Fsdevel Archive on lore.kernel.org
 help / color / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: [ATTEND] many topics
Date: Tue, 17 Jan 2017 21:49:45 -0800
Message-ID: <20170118054945.GD18349@bombadil.infradead.org> (raw)


o/~ There are many things that I would like to say to you ... o/~

mostly around MM and FS interaction.

1. Exploiting multiorder radix tree entries.  I believe we would do well
to attempt to allocate compound pages, insert them into the page cache,
and expect filesystems to be able to handle filling compound pages with
->readpage.  It will be more efficient because alloc_pages() can return
large entries out of the buddy list rather than breaking them down,
and it'll help reduce fragmentation.

2. Supporting filesystem block sizes > page size.  Once we do the above
for efficiency, I think it then becomes trivial to support, eg 16k block
size filesystems on x86 machines with 4k pages.

3. Moving slab objects.  I've been working with Christoph Lameter
this week on implementing a reclaim operation for radix tree nodes.
It seems feasible.  We should probably talk about reclaming dentries
and inodes as well.

4. Pretty much anything relating to DAX.  See other thread.

5. I have discovered a newfound fascination with CIFS which is totally
unrelated to my new employer.  Honest.  I should have some interesting
patches for CIFS by LSFMM.

6. Overhauling vmap to use a radix tree instead of a possibly recursive
vmalloc of an array to store pointers to the pages.

7. Using alloc_pages_exact() to kmalloc objects larger than PAGE_SIZE*2

8. Nailing down exactly what GFP_TEMPORARY means

9. Adding malloc()/free() as a kernel API

I have more things in my IDEAS file, but I think that will do for now.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply index

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  5:49 Matthew Wilcox [this message]
2017-01-18 10:13 ` [Lsf-pc] " Jan Kara
2017-01-18 11:26   ` willy
2017-01-18 13:32 ` Michal Hocko
2017-01-19 11:05   ` willy
2017-01-19 11:33     ` Michal Hocko
2017-01-19 11:52       ` willy
2017-01-19 12:11         ` Michal Hocko
2017-01-21  0:11           ` NeilBrown
2017-01-21 13:16             ` Theodore Ts'o
2017-01-22  4:45               ` NeilBrown
2017-01-23  6:05                 ` Matthew Wilcox
2017-01-23  6:30                   ` NeilBrown
2017-01-23  6:35                     ` Matthew Wilcox
2017-01-23 17:09                   ` Theodore Ts'o
2017-01-23 19:34                     ` NeilBrown
2017-01-25 14:36                       ` Vlastimil Babka
2017-01-25 20:36                         ` Matthew Wilcox
2017-01-25 21:15                           ` Vlastimil Babka
2017-01-25 23:19                         ` NeilBrown
2017-01-26  8:56                           ` Michal Hocko
2017-01-26 21:20                             ` NeilBrown
2017-01-27 13:12                               ` Michal Hocko

Reply instructions:

You may reply publically 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=20170118054945.GD18349@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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

Linux-Fsdevel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-fsdevel/0 linux-fsdevel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-fsdevel linux-fsdevel/ https://lore.kernel.org/linux-fsdevel \
		linux-fsdevel@vger.kernel.org linux-fsdevel@archiver.kernel.org
	public-inbox-index linux-fsdevel


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-fsdevel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox