From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Ming Lei <ming.lei@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH V4 1/3] block: Allow mapping of vmalloc-ed buffers
Date: Thu, 27 Jun 2019 10:25:13 +0200 [thread overview]
Message-ID: <20190627082513.GA11043@lst.de> (raw)
In-Reply-To: <BYAPR04MB581604217983C81B2BA5BA4FE7FD0@BYAPR04MB5816.namprd04.prod.outlook.com>
On Thu, Jun 27, 2019 at 08:17:08AM +0000, Damien Le Moal wrote:
> > Are your sure that invalidate[|flush]_kernel_vmap_range is needed for
> > bio_copy_kernel? The vmalloc buffer isn't involved in IO, and only
> > accessed by CPU.
>
> Not sure at all. I am a little out of my league here.
> Christoph mentioned that this is necessary.
>
> Christoph, can you confirm ?
Ming is right. Sorry for misleading you.
next prev parent reply other threads:[~2019-06-27 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 2:49 [PATCH V4 0/3] Fix zone revalidation memory allocation failures Damien Le Moal
2019-06-27 2:49 ` [PATCH V4 1/3] block: Allow mapping of vmalloc-ed buffers Damien Le Moal
2019-06-27 7:28 ` Christoph Hellwig
2019-06-27 8:14 ` Damien Le Moal
2019-06-27 8:25 ` Christoph Hellwig
2019-06-27 8:37 ` Damien Le Moal
2019-06-27 7:47 ` Ming Lei
2019-06-27 8:17 ` Damien Le Moal
2019-06-27 8:25 ` Christoph Hellwig [this message]
2019-06-27 8:36 ` Damien Le Moal
2019-06-27 2:49 ` [PATCH V4 2/3] sd_zbc: Fix report zones buffer allocation Damien Le Moal
2019-06-27 2:49 ` [PATCH V4 3/3] block: Limit zone array allocation size Damien Le Moal
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=20190627082513.GA11043@lst.de \
--to=hch@lst.de \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@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 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.