public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Matias Bjorling <m@bjorling.me>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] null_blk: documentation, defaults and mapping
Date: Sat, 21 Dec 2013 09:30:00 -0700	[thread overview]
Message-ID: <20131221163000.GE13340@kernel.dk> (raw)
In-Reply-To: <1387581061-25987-1-git-send-email-m@bjorling.me>

On Sat, Dec 21 2013, Matias Bjorling wrote:
> Hi,
> 
> These three patches cover:
> 
> * Incorporated the feedback from Randy Dunlap into documentation.
>   Can be merged with the previous documentation commit (6824518).
> * Set use_per_node_hctx to false per default to save resources.
> * Allow submit_queues and use_per_node_hctx to be used simultanesly.
>   If the submit_queues is a multiple of nr_online_nodes, its trivial. Simply map
>   them to the nodes. For example: 8 submit queues are mapped as node0[0,1],
>   node1[2,3], ...
>   If uneven, we are left with an uneven number of submit_queues that must be
>   mapped. These are mapped toward the first node and onward. E.g. 5
>   submit queues mapped onto 4 nodes are mapped as node0[0,1], node1[2], ...

Thanks, applied.

-- 
Jens Axboe


      parent reply	other threads:[~2013-12-21 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 23:10 [PATCH 0/3] null_blk: documentation, defaults and mapping Matias Bjorling
2013-12-20 23:10 ` [PATCH 1/3] null_blk: corrections to documentation Matias Bjorling
2013-12-21  3:13   ` Randy Dunlap
2013-12-20 23:11 ` [PATCH 2/3] null_blk: set use_per_node_hctx param to false Matias Bjorling
2013-12-20 23:11 ` [PATCH 3/3] null_blk: support submit_queues on use_per_node_hctx Matias Bjorling
2013-12-21 16:30 ` Jens Axboe [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=20131221163000.GE13340@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m@bjorling.me \
    /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