All of lore.kernel.org
 help / color / mirror / Atom feed
From: Honglei Wang <honglei.wang@oracle.com>
To: Michal Hocko <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, vdavydov.dev@gmail.com, hannes@cmpxchg.org
Subject: Re: [PATCH v2] mm/vmscan: get number of pages on the LRU list in memcgroup base on lru_zone_size
Date: Fri, 11 Oct 2019 09:40:59 +0800	[thread overview]
Message-ID: <8926ba7a-9983-5b3f-b726-d1ff1230ef90@oracle.com> (raw)
In-Reply-To: <20191010143313.GJ18412@dhcp22.suse.cz>



On 10/10/19 10:33 PM, Michal Hocko wrote:

> I would just fix the LTP test. Coincidently I have discussed the very
> same thing with our QA guys just recently and the conclusion was to
> update the LTP and use a larger madvised memory area. I haven't checked
> whether this is upstream in LTP already. But please talk to LTP people.
> 
My QA colleague sync with me weeks ago, they have a workaround for this 
case in LTP which is signed-off-by both suse and oracle QA. So it's not 
a problem for LTP now. If we don't care this from kernel side, it's fine 
to drop it.

Thanks,
Honglei

> If there is no other reason to change the kernel code but the failing
> LTP test that doesn't really represent any real life scenario then I
> would simply keep the code as is. Andrew, could you drop it from the
> mmotm tree please?
> 


      reply	other threads:[~2019-10-11  1:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05  7:10 [PATCH v2] mm/vmscan: get number of pages on the LRU list in memcgroup base on lru_zone_size Honglei Wang
2019-10-06  0:10 ` Andrew Morton
2019-10-07 14:28 ` Michal Hocko
2019-10-08  9:34   ` Honglei Wang
2019-10-09 14:16     ` Michal Hocko
2019-10-10  8:40       ` Honglei Wang
2019-10-10 14:33         ` Michal Hocko
2019-10-11  1:40           ` Honglei Wang [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=8926ba7a-9983-5b3f-b726-d1ff1230ef90@oracle.com \
    --to=honglei.wang@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=vdavydov.dev@gmail.com \
    /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.