[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180524131237.soy6jm3ji2pe66id@suse.de>
Date: Thu, 24 May 2018 14:12:37 +0100
From: Mel Gorman <mgorman@...e.de>
To: Jan Kara <jack@...e.cz>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Hugh Dickins <hughd@...gle.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 4.4 50/92] mm: filemap: avoid unnecessary calls to
lock_page when waiting for IO to complete during a read
On Thu, May 24, 2018 at 02:02:37PM +0200, Jan Kara wrote:
> > This is in the SLES kernel for a reason, and again, it's in the section
> > that says "this should be pushed to stable". So if it's good enough for
> > the SLES kernel, why isn't it good enough for all users of this kernel
> > tree?
>
> Heh, fair enough. I guess Mel in the end didn't find patches worthy enough
> to be pushed to stable tree. But at least now I know they are well tested
> with 4.4 base so they should do no harm in the stable tree so my stance is
> closer to neutral.
>
Early on, I backported a number of performance patches to -stable with the
view to having a good baseline to compare a new mainline release with.
However, after a while some of them required unrelated backports that
would be excessive for -stable. While I could have continued backporting
some patches, I stopped as the time required to run all of the performance
tests is excessive and I was already tracking too many kernels.
--
Mel Gorman
SUSE Labs
Powered by blists - more mailing lists