From: Michal Hocko <mhocko@kernel.org>
To: Pankaj Suryawanshi <pankaj.suryawanshi@einfochips.com>
Cc: Kirill Tkhai <ktkhai@virtuozzo.com>,
Vlastimil Babka <vbabka@suse.cz>,
"aneesh.kumar@linux.ibm.com" <aneesh.kumar@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"minchan@kernel.org" <minchan@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"khandual@linux.vnet.ibm.com" <khandual@linux.vnet.ibm.com>
Subject: Re: [External] Re: vmscan: Reclaim unevictable pages
Date: Tue, 26 Mar 2019 10:36:51 +0100 [thread overview]
Message-ID: <20190326093651.GM28406@dhcp22.suse.cz> (raw)
In-Reply-To: <SG2PR02MB3098FAEA335228CFB56F1668E85F0@SG2PR02MB3098.apcprd02.prod.outlook.com>
On Tue 26-03-19 09:16:11, Pankaj Suryawanshi wrote:
>
> ________________________________________
> From: Michal Hocko <mhocko@kernel.org>
> Sent: 26 March 2019 14:31
> To: Pankaj Suryawanshi
> Cc: Kirill Tkhai; Vlastimil Babka; aneesh.kumar@linux.ibm.com; linux-kernel@vger.kernel.org; minchan@kernel.org; linux-mm@kvack.org; khandual@linux.vnet.ibm.com
> Subject: Re: [External] Re: vmscan: Reclaim unevictable pages
>
> [You were asked to use a reasonable quoting several times. This is
> really annoying because it turns the email thread into a complete mess]
>
> [Already fix the email client, but dont know the reason for quoting Maybe account issue.]
You clearly haven't
> As i said earlier, i am using vanilla kernel 4.14.65.
This got lost in the quoting mess. Can you reproduce with 5.0?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-03-26 9:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SG2PR02MB3098A05E09B0D3F3CB1C3B9BE84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>
[not found] ` <SG2PR02MB309806967AE91179CAFEC34BE84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>
[not found] ` <SG2PR02MB3098B751EC6B8E32806A42FBE84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>
[not found] ` <20190314084120.GF7473@dhcp22.suse.cz>
[not found] ` <SG2PR02MB309894F6D7DF9148846088F3E84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>
[not found] ` <226a92b9-94c5-b859-c54b-3aacad3089cc@virtuozzo.com>
[not found] ` <SG2PR02MB3098299456FB6AE2FD822C4CE84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>
[not found] ` <SG2PR02MB30988333AD658F8124070ABEE84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>
2019-03-15 6:05 ` Pankaj Suryawanshi
2019-03-15 10:11 ` Pankaj Suryawanshi
2019-03-18 7:45 ` Pankaj Suryawanshi
2019-03-18 8:56 ` Pankaj Suryawanshi
2019-03-18 8:42 ` [External] " Vlastimil Babka
2019-03-18 9:09 ` Pankaj Suryawanshi
2019-03-18 9:33 ` Kirill Tkhai
2019-03-18 9:43 ` Pankaj Suryawanshi
2019-03-18 9:47 ` Kirill Tkhai
2019-03-18 9:59 ` Pankaj Suryawanshi
2019-03-18 10:38 ` Kirill Tkhai
2019-03-20 6:48 ` Pankaj Suryawanshi
2019-03-26 7:53 ` Pankaj Suryawanshi
2019-03-26 9:01 ` Michal Hocko
2019-03-26 9:12 ` Pankaj Suryawanshi
2019-03-26 9:16 ` Pankaj Suryawanshi
2019-03-26 9:36 ` Michal Hocko [this message]
2019-03-29 5:29 ` Pankaj Suryawanshi
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=20190326093651.GM28406@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=pankaj.suryawanshi@einfochips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox