All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Pankaj Agarwal <pankaj@releasemanager.in>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] how to set higher then 128 nr_requests on LV's
Date: Mon, 14 May 2018 12:13:12 -0400	[thread overview]
Message-ID: <20180514161312.GA14685@redhat.com> (raw)
In-Reply-To: <CAHJ=Ofm_j2B6TeNZR_1GZk40L_fiAqMT=umehupKSnNd+ZHY2A@mail.gmail.com>

On Sun, May 13 2018 at  8:47pm -0400,
Pankaj Agarwal <pankaj@releasemanager.in> wrote:

>    Hi,
>    How do i set the nr_request value for LV's as it's not writable like other
>    drives on a linux system.
>    LV's are set as dm-0 and dm-1 on my system.
>     #cat /sys/block/dm-0/queue/nr_requests
>    128
>    # echo 256 > /sys/block/dm-0/queue/nr_requests
>    -bash: echo: write error: Invalid argument

In the block layer, bio-based devices cannot have their nr_requests
changed, see: block/blk-sysfs.c:queue_requests_store()

So any bio-based DM device (e.g. linear target) won't be allowed to
change nr_requests.

The only way to change this would be from the bottom up:
1) change the underlying request-based device(s) (e.g. /dev/sda)
2) dmsetup suspend + dmsetup resume any bio-based DM device(s) that are
   stacked ontop of the request-based device(s) you changed in 1)
   -- this will restack the queue_limits from the bottom up; so the DM
   device will then reflect the underlying devices' limits.

Mike

  parent reply	other threads:[~2018-05-14 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14  0:47 [linux-lvm] how to set higher then 128 nr_requests on LV's Pankaj Agarwal
2018-05-14 14:21 ` Zdenek Kabelac
2018-05-14 16:13 ` Mike Snitzer [this message]
2018-05-14 17:53   ` Mike Snitzer
2018-05-14 17:53     ` [linux-lvm] " Mike Snitzer
2018-05-14 23:57     ` Pankaj Agarwal
2018-05-14 23:57       ` [linux-lvm] " Pankaj Agarwal
  -- strict thread matches above, loose matches on Subject: below --
2018-05-15  0:22 Mike Snitzer

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=20180514161312.GA14685@redhat.com \
    --to=snitzer@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=pankaj@releasemanager.in \
    /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.