From: Jinyoung Choi <j-young.choi@samsung.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"chaitanya.kulkarni@wdc.com" <chaitanya.kulkarni@wdc.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE:(2) [PATCH v3 0/4] multi-page bvec configuration for integrity payload
Date: Thu, 10 Aug 2023 11:06:15 +0900 [thread overview]
Message-ID: <20230810020615epcms2p8ae414270a3b4cf171fdcd7537fdfbe64@epcms2p8> (raw)
In-Reply-To: <yq1y1ijho3e.fsf@ca-mkp.ca.oracle.com>
Hi, Martin.
> Jinyoung,
>
> > This looks OK to me. I'll test on physical SCSI hardware tomorrow to
> > make sure there are no regressions.
>
> Lab test complete, no regressions seen.
>
> Tested-by: Martin K. Petersen <martin.petersen@oracle.com>
>
> --
> Martin K. Petersen Oracle Linux Engineering
I uploaded only the parts that would not be a problem in the patch-set
I prepared for the first time.
I will prepare to make good use of the nr_integrity_segments in the
request structure.
Thank you for your time.
Have a nice day!
Kind Regards,
Jinyoung.
next prev parent reply other threads:[~2023-08-10 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230803024656epcms2p4da6defb8e1e9b050fe2fbd52cb2e9524@epcms2p4>
2023-08-03 2:46 ` Jinyoung Choi
[not found] ` <CGME20230803024656epcms2p4da6defb8e1e9b050fe2fbd52cb2e9524@epcms2p8>
2023-08-03 2:48 ` [PATCH v3 1/4] block: make bvec_try_merge_hw_page() non-static Jinyoung Choi
2023-08-03 2:52 ` [PATCH v3 4/4] bio-integrity: create multi-page bvecs in bio_integrity_add_page() Jinyoung Choi
2023-08-10 2:06 ` Jinyoung Choi [this message]
[not found] ` <CGME20230803024656epcms2p4da6defb8e1e9b050fe2fbd52cb2e9524@epcms2p3>
2023-08-03 2:49 ` [PATCH v3 2/4] bio-integrity: update the payload size " Jinyoung Choi
[not found] ` <CGME20230803024656epcms2p4da6defb8e1e9b050fe2fbd52cb2e9524@epcms2p5>
2023-08-03 2:50 ` [PATCH v3 3/4] bio-integrity: cleanup adding integrity pages to bip's bvec Jinyoung Choi
2023-08-09 1:36 ` [PATCH v3 0/4] multi-page bvec configuration for integrity payload Martin K. Petersen
2023-08-09 22:04 ` Martin K. Petersen
2023-08-10 13:20 ` Jens Axboe
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=20230810020615epcms2p8ae414270a3b4cf171fdcd7537fdfbe64@epcms2p8 \
--to=j-young.choi@samsung.com \
--cc=axboe@kernel.dk \
--cc=chaitanya.kulkarni@wdc.com \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®