From: Christoph Hellwig <hch@infradead.org>
To: Richard Weinberger <richard@nod.at>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
boris.brezillon@free-electrons.com,
maxime.ripard@free-electrons.com, david@sigma-star.at,
david@fromorbit.com, dedekind1@gmail.com, alex@nextthing.co,
akpm@linux-foundation.org, sasha.levin@oracle.com,
iamjoonsoo.kim@lge.com, rvaswani@codeaurora.org,
tony.luck@intel.com, shailendra.capricorn@gmail.com,
kirill.shutemov@linux.intel.com, hughd@google.com,
mgorman@techsingularity.net, vbabka@suse.cz
Subject: Re: UBIFS and page migration (take 3)
Date: Tue, 17 May 2016 02:11:33 -0700 [thread overview]
Message-ID: <20160517091133.GA23943@infradead.org> (raw)
In-Reply-To: <5739C0C1.1090907@nod.at>
On Mon, May 16, 2016 at 02:44:49PM +0200, Richard Weinberger wrote:
> Is this a Reviewed-by? :-)
I don't know the code well enough to feel qualified for a review. But
you get my:
Acked-by: Christoph Hellwig <hch@lst.de>
> There are two classes of issues:
> a) filesystems that use buffer_migrate_page() but shouldn't
> b) filesystems that don't implement ->migratepage() and fallback_migrate_page()
> is not suitable.
>
> As starter we could kill the automatic assignment of fallback_migrate_page() and
> non-buffer_head filesystems need to figure out whether fallback_migrate_page()
> is suitable or not.
> UBIFS found out the hard way. ;-\
Yes, I think this would be a good start.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Richard Weinberger <richard@nod.at>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
boris.brezillon@free-electrons.com,
maxime.ripard@free-electrons.com, david@sigma-star.at,
david@fromorbit.com, dedekind1@gmail.com, alex@nextthing.co,
akpm@linux-foundation.org, sasha.levin@oracle.com,
iamjoonsoo.kim@lge.com, rvaswani@codeaurora.org,
tony.luck@intel.com, shailendra.capricorn@gmail.com,
kirill.shutemov@linux.intel.com, hughd@google.com,
mgorman@techsingularity.net, vbabka@suse.cz
Subject: Re: UBIFS and page migration (take 3)
Date: Tue, 17 May 2016 02:11:33 -0700 [thread overview]
Message-ID: <20160517091133.GA23943@infradead.org> (raw)
In-Reply-To: <5739C0C1.1090907@nod.at>
On Mon, May 16, 2016 at 02:44:49PM +0200, Richard Weinberger wrote:
> Is this a Reviewed-by? :-)
I don't know the code well enough to feel qualified for a review. But
you get my:
Acked-by: Christoph Hellwig <hch@lst.de>
> There are two classes of issues:
> a) filesystems that use buffer_migrate_page() but shouldn't
> b) filesystems that don't implement ->migratepage() and fallback_migrate_page()
> is not suitable.
>
> As starter we could kill the automatic assignment of fallback_migrate_page() and
> non-buffer_head filesystems need to figure out whether fallback_migrate_page()
> is suitable or not.
> UBIFS found out the hard way. ;-\
Yes, I think this would be a good start.
--
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>
next prev parent reply other threads:[~2016-05-17 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 13:53 UBIFS and page migration (take 3) Richard Weinberger
2016-05-11 13:53 ` Richard Weinberger
2016-05-11 13:53 ` [PATCH 1/2] mm: Export migrate_page_move_mapping and migrate_page_copy Richard Weinberger
2016-05-11 13:53 ` Richard Weinberger
2016-05-11 13:53 ` [PATCH 2/2] UBIFS: Implement ->migratepage() Richard Weinberger
2016-05-11 13:53 ` Richard Weinberger
2016-05-12 10:47 ` Richard Weinberger
2016-05-12 10:47 ` Richard Weinberger
2016-05-12 11:49 ` UBIFS and page migration (take 3) Christoph Hellwig
2016-05-12 11:49 ` Christoph Hellwig
2016-05-16 12:44 ` Richard Weinberger
2016-05-16 12:44 ` Richard Weinberger
2016-05-16 13:03 ` Vlastimil Babka
2016-05-16 13:03 ` Vlastimil Babka
2016-05-17 9:12 ` Christoph Hellwig
2016-05-17 9:12 ` Christoph Hellwig
2016-05-17 11:27 ` Richard Weinberger
2016-05-17 11:27 ` Richard Weinberger
2016-05-18 9:03 ` Richard Weinberger
2016-05-18 9:03 ` Richard Weinberger
2016-05-17 9:11 ` Christoph Hellwig [this message]
2016-05-17 9:11 ` Christoph Hellwig
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=20160517091133.GA23943@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alex@nextthing.co \
--cc=boris.brezillon@free-electrons.com \
--cc=david@fromorbit.com \
--cc=david@sigma-star.at \
--cc=dedekind1@gmail.com \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mgorman@techsingularity.net \
--cc=richard@nod.at \
--cc=rvaswani@codeaurora.org \
--cc=sasha.levin@oracle.com \
--cc=shailendra.capricorn@gmail.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.