From: Pavel Machek <pavel@ucw.cz>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: "Javier González" <javier@javigon.com>,
"Hannes Reinecke" <hare@suse.de>,
"Christoph Hellwig" <hch@lst.de>,
"SelvaKumar S" <selvakuma.s1@samsung.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"Damien Le Moal" <Damien.LeMoal@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>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"snitzer@redhat.com" <snitzer@redhat.com>,
"selvajove@gmail.com" <selvajove@gmail.com>,
"nj.shetty@samsung.com" <nj.shetty@samsung.com>,
"joshi.k@samsung.com" <joshi.k@samsung.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Mikulas Patocka" <mpatocka@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [RFC PATCH v2 0/2] add simple copy support
Date: Wed, 16 Dec 2020 00:45:59 +0100 [thread overview]
Message-ID: <20201215234558.GA18281@amd> (raw)
In-Reply-To: <SN4PR0401MB35983464199FB173FB0C29479BCD0@SN4PR0401MB3598.namprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Hi!
> > Good idea. Are you thinking of a sysfs entry to select the backend?
>
> Not sure on this one, initially I thought of a sysfs file, but then
> how would you do it. One "global" sysfs entry is probably a bad idea.
> Having one per block device to select native vs emulation maybe? And
> a good way to benchmark.
>
> The other idea would be a benchmark loop on boot like the raid library
> does.
Doing copy benchmarking would require writes on the media, right?
Kernel should not do such stuff without userspace requesting it...
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-12-16 0:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201204094719epcas5p23b3c41223897de3840f92ae3c229cda5@epcas5p2.samsung.com>
[not found] ` <20201204094659.12732-1-selvakuma.s1@samsung.com>
2020-12-07 14:11 ` [RFC PATCH v2 0/2] add simple copy support Christoph Hellwig
2020-12-07 14:56 ` Hannes Reinecke
2020-12-07 19:24 ` Javier González
2020-12-08 8:40 ` Johannes Thumshirn
2020-12-08 12:22 ` Javier González
2020-12-08 12:37 ` Johannes Thumshirn
2020-12-08 13:13 ` Javier González
2020-12-08 13:24 ` Johannes Thumshirn
2020-12-09 9:17 ` Javier González
2020-12-15 23:45 ` Pavel Machek [this message]
2020-12-07 22:12 ` Douglas Gilbert
2020-12-08 6:44 ` Hannes Reinecke
2020-12-08 12:21 ` Javier González
2020-12-09 3:02 ` Martin K. Petersen
2020-12-07 19:14 ` Javier González
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=20201215234558.GA18281@amd \
--to=pavel@ucw.cz \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=javier@javigon.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.com \
--cc=nj.shetty@samsung.com \
--cc=sagi@grimberg.me \
--cc=selvajove@gmail.com \
--cc=selvakuma.s1@samsung.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;
as well as URLs for NNTP newsgroup(s).