public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@infradead.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	linux-rdma@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: T10 PI offloading seems to be broken in iser/isert in 4.5/4.6-rc
Date: Sun, 10 Apr 2016 07:37:38 -0700	[thread overview]
Message-ID: <20160410143738.GA14101@infradead.org> (raw)
In-Reply-To: <570A147A.1020601@grimberg.me>

On Sun, Apr 10, 2016 at 11:53:14AM +0300, Sagi Grimberg wrote:
> OK, good to know.
> 
> Since the fabric_prot was added later, I don't think it was properly
> tested (and from what I've seen, not a very interesting use-case).

It's been there for more a year, and once your have non-T10 capable
LUNs in a TPG it gets turned on automatically it seems..

> P.S.
> I'm no longer available in @mellanox.com

I keep messing that all the time by grabbing an address from the list
archives, sorry.  That's why people should only use personal addresses
on mailing lists :)

  reply	other threads:[~2016-04-10 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 22:15 T10 PI offloading seems to be broken in iser/isert in 4.5/4.6-rc Christoph Hellwig
2016-04-08 23:48 ` Nicholas A. Bellinger
2016-04-09  0:14   ` Christoph Hellwig
2016-04-09  2:36     ` Nicholas A. Bellinger
2016-04-09  4:58       ` Christoph Hellwig
     [not found]         ` <20160409045846.GA9269-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-04-10  8:53           ` Sagi Grimberg
2016-04-10 14:37             ` Christoph Hellwig [this message]
2016-04-10 15:30               ` Sagi Grimberg
     [not found]       ` <1460169374.5010.4.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-10  8:42         ` sagig

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=20160410143738.GA14101@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=sagi@grimberg.me \
    --cc=target-devel@vger.kernel.org \
    /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