From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH 1/1] nvme : Add sysfs entry for NVMe CMBs when appropriate
Date: Wed, 05 Oct 2016 11:20:13 -0700 [thread overview]
Message-ID: <1475691613.26632.36.camel@linux.intel.com> (raw)
In-Reply-To: <20161005174841.GA23679@cgy1-donard.priv.deltatee.com>
On Wed, 2016-10-05@11:48 -0600, Stephen Bates wrote:
> On Wed, Oct 05, 2016@07:50:57PM +0300, Sagi Grimberg wrote:
> >
> >
> > >
> > > The fabrics specification currently denotes the CMBLOC and CMBSZ
> > > properties as reserved [1].
> >
> > Managed to forget that... So I guess I'm fine with the patch as
> > it is,
> >
> > Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
> >
>
> Sagi
>
> Thanks! I will work on a v1 to address Jonathan's issue and add your
> tag to that. Coming soon...
You can add my tag too if you like as well, as I've chatted my thoughts
to you via phone/email:
Reviewed-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
>
> >
> > >
> > > Also I am wondering where the physical memory backing a fabrics
> > > CMB
> > > would reside. Would this be memory in the fabric NIC on the host,
> > > in
> > > the NIC on the target or somewhere else?
> >
> > This was discussed in the WG a few times before, not sure if we
> > can discuss this before its in the spec though...
>
> Ooops, you are correct. Us lowely kernel developers should not be
> discussing things related to changes to the NVMe specification ;-). I
> will take this discussion inside the NVMe technical working group.
>
> Cheers
>
> Stephen
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2016-10-05 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 22:15 [PATCH 0/1] nvme : Add sysfs entry for NVMe CMBs when appropriate Stephen Bates
2016-09-27 22:15 ` [PATCH 1/1] " Stephen Bates
2016-09-27 23:17 ` Jon Derrick
2016-09-28 0:10 ` Stephen Bates
2016-10-05 8:22 ` Sagi Grimberg
2016-10-05 14:38 ` Stephen Bates
2016-10-05 16:50 ` Sagi Grimberg
2016-10-05 17:48 ` Stephen Bates
2016-10-05 18:20 ` J Freyensee [this message]
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=1475691613.26632.36.camel@linux.intel.com \
--to=james_p_freyensee@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).