From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet-rdma: move port tsas initialization to rdma code
Date: Thu, 20 Jun 2019 08:29:14 +0200 [thread overview]
Message-ID: <20190620062914.GD20765@lst.de> (raw)
In-Reply-To: <20190619230006.15715-1-sagi@grimberg.me>
On Wed, Jun 19, 2019@04:00:06PM -0700, Sagi Grimberg wrote:
> Also, look at the device transport capability to send
> the correct trtype (ib/roce/rocev2/iwarp). Note that if
> we are listening on addr_any we still return "not specified"
> trtype and the same goes for referrals.
I very much disagree with sending the type. That whole concept
has been a horrible layering violation in the spec that we should
not support.
next prev parent reply other threads:[~2019-06-20 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 23:00 [PATCH] nvmet-rdma: move port tsas initialization to rdma code Sagi Grimberg
2019-06-20 6:29 ` Christoph Hellwig [this message]
2019-06-20 8:02 ` Sagi Grimberg
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=20190620062914.GD20765@lst.de \
--to=hch@lst.de \
/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 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.