From: Greg KH <gregkh@linuxfoundation.org>
To: Shakeel Butt <shakeelb@google.com>
Cc: stable@vger.kernel.org
Subject: Re: Patch "mm, mlock, vmscan: no more skipping pagevecs" has been added to the 4.14-stable tree
Date: Wed, 2 May 2018 08:23:33 -0700 [thread overview]
Message-ID: <20180502152332.GC27126@kroah.com> (raw)
In-Reply-To: <CALvZod6SE5=drNOYJWit_DHp9GhQUpYMA+gF1b_+D2RKA5bWxQ@mail.gmail.com>
On Wed, May 02, 2018 at 12:51:15AM +0000, Shakeel Butt wrote:
> On Tue, May 1, 2018 at 4:52 PM <gregkh@linuxfoundation.org> wrote:
>
>
> > This is a note to let you know that I've just added the patch titled
>
> > mm, mlock, vmscan: no more skipping pagevecs
>
> > to the 4.14-stable tree which can be found at:
>
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> > The filename of the patch is:
> > mm-mlock-vmscan-no-more-skipping-pagevecs.patch
> > and it can be found in the queue-4.14 subdirectory.
>
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
>
> I would advise not to include this patch in the previous stable trees. This
> patch does not fix any critical bug and for some very specific
> microbenchmarks on very large machines, it has shown performance
> regression. So, I don't think it is worth the risk.
thanks, now dropped. Hopefully this gets fixed in Linus's tree :)
greg k-h
prev parent reply other threads:[~2018-05-02 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1525218534194@kroah.com>
2018-05-02 0:51 ` Patch "mm, mlock, vmscan: no more skipping pagevecs" has been added to the 4.14-stable tree Shakeel Butt
2018-05-02 15:23 ` Greg KH [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=20180502152332.GC27126@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=shakeelb@google.com \
--cc=stable@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 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.