Linux Device Mapper development
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	dm-devel@redhat.com, Mike Snitzer <snitzer@redhat.com>
Subject: Re: dm_set_target_max_io_len
Date: Thu, 21 Mar 2019 19:14:58 +0800	[thread overview]
Message-ID: <20190321111457.GA23305@ming.t460p> (raw)
In-Reply-To: <alpine.LRH.2.02.1903210621110.17154@file01.intranet.prod.int.rdu2.redhat.com>

Hi Mikulas,

On Thu, Mar 21, 2019 at 06:33:32AM -0400, Mikulas Patocka wrote:
> Hi
> 
> I'm looking at the patch 8f50e358153dd68182c714626be4a90b64179cf4. The 
> patch claims that dm-crypt can't deal with large bios - but I fixed this 
> problem with dm-crypt a year before (see the patch 
> 4e870e948fbabf62b78e8410f04c67703e7c816b). Was my fix for dm-crypt 
> inefficient? Can you provide some test where dm-crypt fails with big bios?

Sorry for missing the commit 4e870e948fbabf62b78e8410f04c67703e7c816b.

> 
> Should 8f50e358153dd68182c714626be4a90b64179cf4 be dropped? The variable 

Yeah, I think so.

Thanks,
Ming

      reply	other threads:[~2019-03-21 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 10:33 dm_set_target_max_io_len Mikulas Patocka
2019-03-21 11:14 ` Ming Lei [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=20190321111457.GA23305@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox