public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] madvise09:Change PAGES size to the value more than 32
Date: Wed, 11 Sep 2019 13:19:00 +0200	[thread overview]
Message-ID: <20190911111900.GA19244@rei.lan> (raw)
In-Reply-To: <CAEemH2fiJkau0A3yQH+nHVPXMwtTzyV3_weTQRniZFR+EJqN_g@mail.gmail.com>

Hi!
> I'm not sure why 64 pages is a proper value? Can you explain more?

I've just talked to Michal Hocko and the conclusion is that we should
allocate several megabytes to avoid depending kernel implementation
details, which would mean allocating thousands of pages.

-- 
Cyril Hrubis
chrubis@suse.cz

  parent reply	other threads:[~2019-09-11 11:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  6:00 [LTP] [PATCH] madvise09:Change PAGES size to the value more than 32 shuang.qiu
2019-09-04 14:32 ` Thadeu Lima de Souza Cascardo
2019-09-05  8:29 ` Li Wang
2019-09-05 10:01   ` Shuang Qiu
2019-09-05 10:29     ` Li Wang
2019-09-11 11:19   ` Cyril Hrubis [this message]
2019-09-12  2:51     ` Li Wang
2019-09-12  3:35       ` Shuang Qiu

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=20190911111900.GA19244@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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