All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Hannes Reinecke <hare@suse.de>,
	linux-block@vger.kernel.org, Mel Gorman <mgorman@suse.com>,
	Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH] brd: Allow ramdisk to be allocated on selected NUMA node
Date: Fri, 15 Jun 2018 00:30:35 -0700	[thread overview]
Message-ID: <20180615073035.GA15535@infradead.org> (raw)
In-Reply-To: <656e4ab7-7c5c-41af-5596-2e155ffb28e4@kernel.dk>

On Thu, Jun 14, 2018 at 09:33:35AM -0600, Jens Axboe wrote:
> Next question - what does the memory allocator do if we run out of
> memory on the given node? Should we punt to a different node if that
> happens? Slower, but functional, seems preferable to not being able
> to get memory.

When using alloc_pages_node the passed in node id is just a hint, the
allocator will use all avaiable memory if nedeed.

  parent reply	other threads:[~2018-06-15  7:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14 13:38 [PATCH] brd: Allow ramdisk to be allocated on selected NUMA node Hannes Reinecke
2018-06-14 14:47 ` Jens Axboe
2018-06-14 15:29   ` Hannes Reinecke
2018-06-14 15:33     ` Jens Axboe
2018-06-14 16:09       ` Hannes Reinecke
2018-06-14 20:32         ` Adam Manzanares
2018-06-14 20:37           ` Jens Axboe
2018-06-14 20:41             ` Adam Manzanares
2018-06-14 20:47               ` Jens Axboe
2018-06-14 20:53                 ` Adam Manzanares
2018-06-15  6:06                   ` Hannes Reinecke
2018-06-15  9:23                 ` Mel Gorman
2018-06-15 14:28                   ` Jens Axboe
2018-06-15  7:30       ` Christoph Hellwig [this message]
2018-06-15 14:12         ` Jens Axboe
2018-06-15 14:07 ` Bart Van Assche
2018-06-15 16:55   ` Hannes Reinecke
2018-06-15 16:58     ` Bart Van Assche

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=20180615073035.GA15535@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.com \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=mgorman@suse.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.