From: Damien Le Moal <Damien.LeMoal@wdc.com> To: Sergei Shtepa <sergei.shtepa@veeam.com>, "hare@suse.de" <hare@suse.de>, "ming.lei@redhat.com" <ming.lei@redhat.com>, "agk@redhat.com" <agk@redhat.com>, "snitzer@redhat.com" <snitzer@redhat.com>, "dm-devel@redhat.com" <dm-devel@redhat.com>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org> Cc: "pavel.tide@veeam.com" <pavel.tide@veeam.com> Subject: Re: [dm-devel] [PATCH 0/2] block: blk_interposer v3 Date: Fri, 29 Jan 2021 00:18:19 +0000 [thread overview] Message-ID: <BL0PR04MB6514A510F37C59F52D87E2EDE7B99@BL0PR04MB6514.namprd04.prod.outlook.com> (raw) In-Reply-To: 1611853955-32167-1-git-send-email-sergei.shtepa@veeam.com On 2021/01/29 2:23, Sergei Shtepa wrote: > Hi all, > > I`m ready to suggest the blk_interposer again. > blk_interposer allows to intercept bio requests, remap bio to > another devices or add new bios. > > This version has support from device mapper. > > For the dm-linear device creation command, the `noexcl` parameter > has been added, which allows to open block devices without > FMODE_EXCL mode. It allows to create dm-linear device on a block > device with an already mounted file system. > The new ioctl DM_DEV_REMAP allows to enable and disable bio > interception. > > Thus, it is possible to add the dm-device to the block layer stack > without reconfiguring and rebooting. Please add the changelog here instead of adding it in each patch. And keep the changelog for previous versions too (i.e. v1->v2 in this case) so that the changes overall can be tracked. The proper formatting for the title should be [PATCH v3 X/Y] instead of adding v3 in the title itself. With git format-patch, you can use "-v 3" option to format this for you, or --subject-prefix="PATCH v3" option. > > > Sergei Shtepa (2): > block: blk_interposer > [dm] blk_interposer for dm-linear > > block/bio.c | 2 + > block/blk-core.c | 29 +++ > block/blk-mq.c | 13 ++ > block/genhd.c | 82 ++++++++ > drivers/md/dm-core.h | 46 +++- > drivers/md/dm-ioctl.c | 39 ++++ > drivers/md/dm-linear.c | 17 +- > drivers/md/dm-table.c | 12 +- > drivers/md/dm.c | 383 ++++++++++++++++++++++++++++++++-- > drivers/md/dm.h | 2 +- > include/linux/blk-mq.h | 1 + > include/linux/blk_types.h | 6 +- > include/linux/device-mapper.h | 7 + > include/linux/genhd.h | 19 ++ > include/uapi/linux/dm-ioctl.h | 15 +- > 15 files changed, 643 insertions(+), 30 deletions(-) > -- Damien Le Moal Western Digital Research
WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <Damien.LeMoal@wdc.com> To: Sergei Shtepa <sergei.shtepa@veeam.com>, "hare@suse.de" <hare@suse.de>, "ming.lei@redhat.com" <ming.lei@redhat.com>, "agk@redhat.com" <agk@redhat.com>, "snitzer@redhat.com" <snitzer@redhat.com>, "dm-devel@redhat.com" <dm-devel@redhat.com>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org> Cc: "pavel.tide@veeam.com" <pavel.tide@veeam.com> Subject: Re: [dm-devel] [PATCH 0/2] block: blk_interposer v3 Date: Fri, 29 Jan 2021 00:18:19 +0000 [thread overview] Message-ID: <BL0PR04MB6514A510F37C59F52D87E2EDE7B99@BL0PR04MB6514.namprd04.prod.outlook.com> (raw) In-Reply-To: 1611853955-32167-1-git-send-email-sergei.shtepa@veeam.com On 2021/01/29 2:23, Sergei Shtepa wrote: > Hi all, > > I`m ready to suggest the blk_interposer again. > blk_interposer allows to intercept bio requests, remap bio to > another devices or add new bios. > > This version has support from device mapper. > > For the dm-linear device creation command, the `noexcl` parameter > has been added, which allows to open block devices without > FMODE_EXCL mode. It allows to create dm-linear device on a block > device with an already mounted file system. > The new ioctl DM_DEV_REMAP allows to enable and disable bio > interception. > > Thus, it is possible to add the dm-device to the block layer stack > without reconfiguring and rebooting. Please add the changelog here instead of adding it in each patch. And keep the changelog for previous versions too (i.e. v1->v2 in this case) so that the changes overall can be tracked. The proper formatting for the title should be [PATCH v3 X/Y] instead of adding v3 in the title itself. With git format-patch, you can use "-v 3" option to format this for you, or --subject-prefix="PATCH v3" option. > > > Sergei Shtepa (2): > block: blk_interposer > [dm] blk_interposer for dm-linear > > block/bio.c | 2 + > block/blk-core.c | 29 +++ > block/blk-mq.c | 13 ++ > block/genhd.c | 82 ++++++++ > drivers/md/dm-core.h | 46 +++- > drivers/md/dm-ioctl.c | 39 ++++ > drivers/md/dm-linear.c | 17 +- > drivers/md/dm-table.c | 12 +- > drivers/md/dm.c | 383 ++++++++++++++++++++++++++++++++-- > drivers/md/dm.h | 2 +- > include/linux/blk-mq.h | 1 + > include/linux/blk_types.h | 6 +- > include/linux/device-mapper.h | 7 + > include/linux/genhd.h | 19 ++ > include/uapi/linux/dm-ioctl.h | 15 +- > 15 files changed, 643 insertions(+), 30 deletions(-) > -- Damien Le Moal Western Digital Research -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-01-29 0:19 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-28 17:12 [PATCH 0/2] block: blk_interposer v3 Sergei Shtepa 2021-01-28 17:12 ` [dm-devel] " Sergei Shtepa 2021-01-28 17:12 ` [PATCH 1/2] block: blk_interposer Sergei Shtepa 2021-01-28 17:12 ` [dm-devel] " Sergei Shtepa 2021-01-29 1:21 ` Damien Le Moal 2021-01-29 1:21 ` Damien Le Moal 2021-01-29 15:58 ` Sergei Shtepa 2021-01-28 17:12 ` [PATCH 2/2] [dm] blk_interposer for dm-linear Sergei Shtepa 2021-01-28 17:12 ` [dm-devel] " Sergei Shtepa 2021-01-29 1:46 ` Damien Le Moal 2021-01-29 1:46 ` Damien Le Moal 2021-01-29 16:08 ` Sergei Shtepa 2021-01-29 16:08 ` Sergei Shtepa 2021-01-29 0:18 ` Damien Le Moal [this message] 2021-01-29 0:18 ` [dm-devel] [PATCH 0/2] block: blk_interposer v3 Damien Le Moal 2021-01-29 15:39 ` Sergei Shtepa 2021-02-01 15:45 ` Bart Van Assche 2021-02-01 15:45 ` Bart Van Assche 2021-02-01 18:18 ` Sergei Shtepa 2021-02-01 18:18 ` Sergei Shtepa 2021-02-01 18:50 ` Mike Snitzer 2021-02-01 18:50 ` [dm-devel] " Mike Snitzer 2021-02-02 1:24 ` Sergei Shtepa 2021-02-02 1:24 ` [dm-devel] " Sergei Shtepa
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=BL0PR04MB6514A510F37C59F52D87E2EDE7B99@BL0PR04MB6514.namprd04.prod.outlook.com \ --to=damien.lemoal@wdc.com \ --cc=agk@redhat.com \ --cc=dm-devel@redhat.com \ --cc=hare@suse.de \ --cc=linux-block@vger.kernel.org \ --cc=ming.lei@redhat.com \ --cc=pavel.tide@veeam.com \ --cc=sergei.shtepa@veeam.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: linkBe 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.