Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "damien.lemoal@opensource.wdc.com"
	<damien.lemoal@opensource.wdc.com>,
	"johannes.thumshirn@wdc.com" <johannes.thumshirn@wdc.com>,
	"bvanassche@acm.org" <bvanassche@acm.org>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"vincent.fu@samsung.com" <vincent.fu@samsung.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
	"error27@gmail.com" <error27@gmail.com>
Subject: Re: [PATCH 0/4] null_blk: usr memcpy_[to|from]_page()
Date: Thu, 30 Mar 2023 17:00:48 -0600	[thread overview]
Message-ID: <b14876d0-8ca1-4a7e-e228-aebc0d2b243c@kernel.dk> (raw)
In-Reply-To: <02b39d4a-821b-0b86-5a64-7d4a706b79b8@nvidia.com>

On 3/30/23 12:56?PM, Chaitanya Kulkarni wrote:
> On 3/29/23 15:48, Jens Axboe wrote:
>> On 3/29/23 2:46?PM, Chaitanya Kulkarni wrote:
>>> Hi,
>>>
>>>  From :include/linux/highmem.h:
>>> "kmap_atomic - Atomically map a page for temporary usage - Deprecated!"
>>>
>>> Use memcpy_from_page() since does the same job of mapping, copying, and
>>> unmaping except it uses non deprecated kmap_local_page() and
>>> kunmap_local(). Following are the differences between kmal_local_page()
>>> and kmap_atomic() :-
>> Looks fine to me, but I'd fold patches 1-3 rather than split them up.
>>
> 
> Sent V2 with above comment, first three patches are from
> different code path and they are doing unrelated changes:-
> 
> 1. WRITE :- copy_to_nullb() only use memcpy_page().
> 2. READ :- copy_from_nullb() only use memcapy_page() and zero_user().
> 3. I guess zoned read beyond write pointer null_fill_pattern()
>     memset_page().
> 
> if anything goes wrong in any of 3 code paths we will have to
> entire change which we shouldn't, that's why kept it separate,
> I'm fine with whatever you decide ...

It doesn't matter... It's not like this is a hugely complicated thing.
It's just a straight forward conversion. They all just switch to using a
helper, which is the right thing to do as it reduces the stuff we have
to do in there. Only reason why I excluded patch 4 is that it is a bit
different than the others. But it really could just be one patch.

-- 
Jens Axboe


      reply	other threads:[~2023-03-30 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 20:46 [PATCH 0/4] null_blk: usr memcpy_[to|from]_page() Chaitanya Kulkarni
2023-03-29 20:46 ` [PATCH 1/4] null_blk: use memcpy_page() in copy_to_nullb() Chaitanya Kulkarni
2023-03-29 20:46 ` [PATCH 2/4] null_blk: use memcpy_page() in copy_from_nullb() Chaitanya Kulkarni
2023-03-29 20:46 ` [PATCH 3/4] null-blk: use memset_page() to fill page pattern Chaitanya Kulkarni
2023-03-29 20:46 ` [PATCH 4/4] null_blk: use kmap_local_page() and kunmap_local() Chaitanya Kulkarni
2023-03-29 22:48 ` [PATCH 0/4] null_blk: usr memcpy_[to|from]_page() Jens Axboe
2023-03-30 18:56   ` Chaitanya Kulkarni
2023-03-30 23:00     ` 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=b14876d0-8ca1-4a7e-e228-aebc0d2b243c@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=chaitanyak@nvidia.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=error27@gmail.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=vincent.fu@samsung.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