From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
linux-mm@kvack.org, linux-xfs@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] File system memory management topics
Date: Mon, 05 Feb 2018 12:31:04 +0530 [thread overview]
Message-ID: <9098480.msMr5zvJja@dhcp-9-109-247-41> (raw)
In-Reply-To: <20180201143422.phir5f2wwv6udnqe@destiny>
On Thursday, February 1, 2018 8:04:22 PM IST Josef Bacik wrote:
> Hello,
>
> I've been lazily working through various mm related issues with file systems for
> the last couple of years and would like to talk about current progress and work
> thats left to be done. Some of the topics I want to cover are
>
> * Metadata tracking, writeback, and reclaim
> * Smarter fs cache shrinking
> * Non-page size block size handling
>
The above list of items mentioned by Josef is very important (especially w.r.t
Btrfs' subpage-blocksize support) for getting 4k blocksized filesystems to
work well for architectures like PPC64 and AARCH64 which [can] have 64k page
size. Hence I would request that these topics gets discussed during this
year's LSF/MM summit.
> Dave please tell me you are going to be there this year? It's going to be
> completely useless for me to talk about this stuff if you aren't in the room.
> These are all big topics in and of themselves so if we just need to get you, me,
> Jan, and some poor MM guy locked in a room with a couple of bottles of liquor
> until we figure it out then that's fine.
>
> I'm hoping to have the metadata tracking stuff fixed up and at least mergable by
> LSF, but there's still stuff to be added to that infrastructure later on, and
> the other topics we need to agree on a direction. Thanks,
>
--
chandan
--
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>
prev parent reply other threads:[~2018-02-05 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 14:34 Josef Bacik
2018-02-05 7:01 ` Chandan Rajendra [this message]
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=9098480.msMr5zvJja@dhcp-9-109-247-41 \
--to=chandan@linux.vnet.ibm.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.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
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