From: Mikulas Patocka <mpatocka@redhat.com> To: Jens Axboe <axboe@kernel.dk>, Zdenek Kabelac <zkabelac@redhat.com> Cc: linux-block@vger.kernel.org, dm-devel@redhat.com Subject: [PATCH 0/4] brd: implement discard Date: Fri, 16 Sep 2022 04:58:54 -0400 (EDT) [thread overview] Message-ID: <alpine.LRH.2.02.2209151604410.13231@file01.intranet.prod.int.rdu2.redhat.com> (raw) Hi This series of patches implements discard, write_zeroes and secure_erase support for the brd driver. Zdenek asked me to write it, because we use brd in the lvm2 testsuite and it would be benefical to run the testsuite with discard enabled in order to test discard handling. This patch series should have no performance impact - it doesn't add any locks to the common I/O paths. It only extends rcu read region around lookup and reading or writing of a single page. Discarded pages are freed with "call_rcu" to make sure that if we mix discard with I/O, the I/O won't access freed memory. Mikulas
WARNING: multiple messages have this Message-ID (diff)
From: Mikulas Patocka <mpatocka@redhat.com> To: Jens Axboe <axboe@kernel.dk>, Zdenek Kabelac <zkabelac@redhat.com> Cc: linux-block@vger.kernel.org, dm-devel@redhat.com Subject: [dm-devel] [PATCH 0/4] brd: implement discard Date: Fri, 16 Sep 2022 04:58:54 -0400 (EDT) [thread overview] Message-ID: <alpine.LRH.2.02.2209151604410.13231@file01.intranet.prod.int.rdu2.redhat.com> (raw) Hi This series of patches implements discard, write_zeroes and secure_erase support for the brd driver. Zdenek asked me to write it, because we use brd in the lvm2 testsuite and it would be benefical to run the testsuite with discard enabled in order to test discard handling. This patch series should have no performance impact - it doesn't add any locks to the common I/O paths. It only extends rcu read region around lookup and reading or writing of a single page. Discarded pages are freed with "call_rcu" to make sure that if we mix discard with I/O, the I/O won't access freed memory. Mikulas -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2022-09-16 8:59 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-16 8:58 Mikulas Patocka [this message] 2022-09-16 8:58 ` [dm-devel] [PATCH 0/4] brd: implement discard Mikulas Patocka 2022-09-16 8:59 ` [PATCH 1/4] brd: make brd_insert_page return bool Mikulas Patocka 2022-09-16 8:59 ` [dm-devel] " Mikulas Patocka 2022-09-20 7:28 ` Christoph Hellwig 2022-09-20 7:28 ` [dm-devel] " Christoph Hellwig 2022-09-16 8:59 ` [PATCH 2/4] brd: extend the rcu regions to cover read and write Mikulas Patocka 2022-09-16 8:59 ` [dm-devel] " Mikulas Patocka 2022-09-20 7:38 ` Christoph Hellwig 2022-09-20 7:38 ` [dm-devel] " Christoph Hellwig 2022-09-16 9:00 ` [dm-devel] [PATCH 3/4] brd: enable discard Mikulas Patocka 2022-09-16 9:00 ` Mikulas Patocka 2022-09-20 7:39 ` [dm-devel] " Christoph Hellwig 2022-09-20 7:39 ` Christoph Hellwig 2022-09-20 17:47 ` [dm-devel] " Mikulas Patocka 2022-09-20 17:47 ` Mikulas Patocka 2022-09-16 9:00 ` [dm-devel] [PATCH 4/4] brd: implement secure erase and write zeroes Mikulas Patocka 2022-09-16 9:00 ` Mikulas Patocka 2022-09-20 7:29 ` Christoph Hellwig 2022-09-20 7:29 ` [dm-devel] " Christoph Hellwig 2022-09-20 17:46 ` Mikulas Patocka 2022-09-20 17:46 ` Mikulas Patocka
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=alpine.LRH.2.02.2209151604410.13231@file01.intranet.prod.int.rdu2.redhat.com \ --to=mpatocka@redhat.com \ --cc=axboe@kernel.dk \ --cc=dm-devel@redhat.com \ --cc=linux-block@vger.kernel.org \ --cc=zkabelac@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.