All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "john@stoffel.org" <john@stoffel.org>,
	"mpatocka@redhat.com" <mpatocka@redhat.com>
Cc: "msnitzer@redhat.com" <msnitzer@redhat.com>,
	"tom.ty89@gmail.com" <tom.ty89@gmail.com>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>,
	"okozina@redhat.com" <okozina@redhat.com>,
	"hch@lst.de" <hch@lst.de>, "mbroz@redhat.com" <mbroz@redhat.com>
Subject: Re: [PATCH] dm-crypt: limit the number of allocated pages
Date: Sat, 19 Aug 2017 00:59:12 +0000	[thread overview]
Message-ID: <1503104350.2620.1.camel@wdc.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1708181523190.30782@file01.intranet.prod.int.rdu2.redhat.com>

On Fri, 2017-08-18 at 20:18 -0400, Mikulas Patocka wrote:
> Some times ago I made a patch that limits the number of in-flight bios in 
> device mapper - see this:
> http://people.redhat.com/~mpatocka/patches/kernel/dm-limit-outstanding-bios/

It would be great to have this functionality upstream ... Do you have any
plans to submit this patch to the device mapper maintainer, Mike Snitzer?

Bart.

  reply	other threads:[~2017-08-19  0:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14  2:45 [PATCH] dm-crypt: limit the number of allocated pages Mikulas Patocka
2017-08-14 20:19 ` John Stoffel
2017-08-15  0:07   ` Mikulas Patocka
2017-08-17 18:50     ` John Stoffel
2017-08-18 16:58       ` Mikulas Patocka
2017-08-18 19:02         ` John Stoffel
2017-08-19  0:18           ` Mikulas Patocka
2017-08-19  0:59             ` Bart Van Assche [this message]
2017-08-21 14:06             ` John Stoffel
2017-08-14 20:22 ` Tom Yan
2017-08-15  0:20   ` Mikulas Patocka
2017-08-15 16:51     ` Tom Yan
2017-08-19 17:34       ` Mikulas Patocka
2017-08-25  4:58         ` Tom Yan
2017-09-11 23:57           ` Mikulas Patocka

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=1503104350.2620.1.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@lst.de \
    --cc=john@stoffel.org \
    --cc=mbroz@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=msnitzer@redhat.com \
    --cc=okozina@redhat.com \
    --cc=tom.ty89@gmail.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.