mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jinpu Wang <jinpu.wang@ionos.com>
Cc: kernel test robot <oliver.sang@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, lkp@lists.01.org, lkp@intel.com,
	"Md. Haris Iqbal" <haris.iqbal@ionos.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
	linux-rdma@vger.kernel.org
Subject: Re: [locking/lockdep] 4051a81774: page_allocation_failure:order:#,mode:#(GFP_KERNEL),nodemask=(null)
Date: Wed, 22 Jun 2022 08:43:46 +0200	[thread overview]
Message-ID: <YrK6Iv5jsBa7BRrL@linutronix.de> (raw)
In-Reply-To: <CAMGffEksZGQrdHM9CS0H0Tq4TvfQMAbdcFYZej2KNWY=VxuBQg@mail.gmail.com>

On 2022-06-21 17:27:22 [+0200], Jinpu Wang wrote:
> Hi, there
Hi,

> > > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> > >
> > …
> > > [   17.451787][    T1] rtrs_server L2256: Loading module rtrs_server, proto 2.0: (max_chunk_size: 131072 (pure IO 126976, headers 4096) , sess_queue_depth: 512, always_invalidate: 1)
> > > [   17.470894][    T1] swapper: page allocation failure: order:5, mode:0xcc0(GFP_KERNEL), nodemask=(null)
> >
> > If I read this right, it allocates "512 * 10" chunks of order 5 / 128KiB
> > of memory (contiguous memory). And this appears to fail.
> > This is either a lot of memory or something that shouldn't be used on
> > i386.
> It allocates 512 * 128 KiB of memory, which is probably to big for
> this VM setup.

why 512 * 128KiB? It is:
|         chunk_pool = mempool_create_page_pool(sess_queue_depth * CHUNK_POOL_SZ,
|                                               get_order(max_chunk_size));
with
| static int __read_mostly max_chunk_size = DEFAULT_MAX_CHUNK_SIZE;
| static int __read_mostly sess_queue_depth = DEFAULT_SESS_QUEUE_DEPTH;
| #define CHUNK_POOL_SZ 10

so isn't it (512 * 10) * 128KiB?

> Thanks!

Sebastian

  reply	other threads:[~2022-06-22  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  2:07 kernel test robot
2022-06-20  9:42 ` Sebastian Andrzej Siewior
2022-06-21 15:27   ` Jinpu Wang
2022-06-22  6:43     ` Sebastian Andrzej Siewior [this message]
2022-06-22  6:56       ` Jinpu Wang

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=YrK6Iv5jsBa7BRrL@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=haris.iqbal@ionos.com \
    --cc=jgg@ziepe.ca \
    --cc=jinpu.wang@ionos.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=peterz@infradead.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®