From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-nvme@lists.infradead.org
Cc: MRuijter@onestopsystems.com, hch@lst.de,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
sagi@grimberg.me
Subject: [PATCH 0/2] nvmet: bdev-ns buffered-io and file-ns write-through
Date: Tue, 4 Feb 2020 18:01:18 -0800 [thread overview]
Message-ID: <20200205020120.22210-1-chaitanya.kulkarni@wdc.com> (raw)
Hi,
These are last two patches which are based on the discussion with Mark
(CCd here) along with cntlid and mode.
This patch series adds a support for block device namespace to use
cache and file-backed namespace to use cache in write-through.
Please have a look at the respective commit logs for more details.
Regards,
Chaitanya
Chaitanya Kulkarni (2):
nvmet: allow block device to use buffered I/O
nvmet: add file-backed ns write-through support
drivers/nvme/target/configfs.c | 72 +++++++++++++++++++++++++++++++
drivers/nvme/target/core.c | 7 ++-
drivers/nvme/target/io-cmd-bdev.c | 3 ++
drivers/nvme/target/io-cmd-file.c | 39 ++++++++++++-----
drivers/nvme/target/nvmet.h | 15 +++++++
5 files changed, 125 insertions(+), 11 deletions(-)
--
2.22.1
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-02-05 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 2:01 Chaitanya Kulkarni [this message]
2020-02-05 2:01 ` [PATCH RESEND V2 1/2] nvmet: allow block device to use buffered I/O Chaitanya Kulkarni
2020-02-11 17:22 ` Sagi Grimberg
2020-02-11 17:58 ` Chaitanya Kulkarni
2020-02-05 2:01 ` [PATCH 2/2] nvmet: add file-backed ns write-through support Chaitanya Kulkarni
-- strict thread matches above, loose matches on Subject: below --
2020-02-05 1:56 [PATCH 0/2] nvmet: bdev-ns buffered-io and file-ns write-through Chaitanya Kulkarni
2020-02-05 1:56 ` Chaitanya Kulkarni
2020-02-05 1:59 ` Chaitanya Kulkarni
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=20200205020120.22210-1-chaitanya.kulkarni@wdc.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=MRuijter@onestopsystems.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).