From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH V5] nvmet: add simple file backed ns support
Date: Thu, 17 May 2018 15:14:37 -0600 [thread overview]
Message-ID: <20180517211436.GH23555@localhost.localdomain> (raw)
In-Reply-To: <20180517124714.GA31470@lst.de>
On Thu, May 17, 2018@02:47:14PM +0200, Christoph Hellwig wrote:
> On Thu, May 17, 2018@01:45:58AM -0400, Chaitanya Kulkarni wrote:
> > The new file io-cmd-file.c is responsible for handling
> > the code for I/O commands when ns is file backed. Also,
> > we introduce mempools based slow path for file backed
> > ns.
>
> Please use ~ 73 lines for the changelog to instead of line wrapping
> earlier.
Useful tip for vi users: http://vim.wikia.com/wiki/Chop_long_lines
The same method can combine shorter lines.
next prev parent reply other threads:[~2018-05-17 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 5:45 [PATCH V5] nvmet: add simple file backed ns support Chaitanya Kulkarni
2018-05-17 12:47 ` Christoph Hellwig
2018-05-17 21:14 ` Keith Busch [this message]
2018-05-17 22:39 ` Chaitanya Kulkarni
2018-05-18 9:06 ` Christoph Hellwig
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=20180517211436.GH23555@localhost.localdomain \
--to=keith.busch@linux.intel.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).