From: sagi@grimberg.me (Sagi Grimberg)
Subject: [LSF/MM TOPIC] NVMe over Fabrics auto-discovery in Linux
Date: Wed, 24 Jan 2018 20:59:05 +0200 [thread overview]
Message-ID: <9b317edd-d2e2-a4e8-d419-fbc5699bd33f@grimberg.me> (raw)
In-Reply-To: <95f83103-fa9b-7d20-723e-e2aaa8cc1276@broadcom.com>
>> FC can keep doing its own thing...
>>
>
> :)? Funny, I see it as ethernet solutions keep doing their own thing
> with each new protocol. FC keeps doing what it has for years.
I meant "its own mature well-known that works thing" :)
next prev parent reply other threads:[~2018-01-24 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 15:11 [LSF/MM TOPIC] NVMe over Fabrics auto-discovery in Linux Johannes Thumshirn
2018-01-23 16:09 ` Bart Van Assche
2018-01-24 8:26 ` Hannes Reinecke
2018-01-24 17:17 ` James Smart
2018-01-24 18:46 ` Sagi Grimberg
2018-01-24 18:42 ` Sagi Grimberg
2018-01-24 18:51 ` James Smart
2018-01-24 18:59 ` Sagi Grimberg [this message]
2018-01-29 13:05 ` Johannes Thumshirn
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=9b317edd-d2e2-a4e8-d419-fbc5699bd33f@grimberg.me \
--to=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