From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: I/O Errors due to keepalive timeouts with NVMf RDMA
Date: Tue, 11 Jul 2017 10:52:04 +0200 [thread overview]
Message-ID: <20170711085204.GA7846@linux-x5ow.site> (raw)
In-Reply-To: <4df0a8a8-168f-06c4-6112-dfd2893d6e06@grimberg.me>
On Mon, Jul 10, 2017@03:04:52PM +0300, Sagi Grimberg wrote:
> And if your keep-alive did not make it in 35 seconds, then its an
> indication that something is wrong... which is exactly what keep-alives
> are designed to do... So I'm not at all sure that we need to compensate
> for this in the driver at all, something is clearly wrong in your
> fabric.
Not that I disagree with you, but two different (not connected) fabrics
(OmniPath and IB) and both are broken, while I see no problems on IPoIB?
Not sure how likely this is.
But still trying to figure out what's going on.
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-07-11 8:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 9:48 I/O Errors due to keepalive timeouts with NVMf RDMA Johannes Thumshirn
2017-07-08 18:14 ` Max Gurtovoy
2017-07-10 7:59 ` Johannes Thumshirn
2017-07-10 7:06 ` Sagi Grimberg
2017-07-10 7:17 ` Hannes Reinecke
2017-07-10 8:46 ` Max Gurtovoy
2017-07-10 9:10 ` Johannes Thumshirn
2017-07-10 10:13 ` Sagi Grimberg
2017-07-10 10:20 ` Johannes Thumshirn
2017-07-10 11:04 ` Sagi Grimberg
2017-07-10 11:33 ` Johannes Thumshirn
2017-07-10 11:41 ` Sagi Grimberg
2017-07-10 11:50 ` Johannes Thumshirn
2017-07-10 12:04 ` Sagi Grimberg
2017-07-11 8:52 ` Johannes Thumshirn [this message]
2017-07-11 9:19 ` Sagi Grimberg
2017-07-11 9:21 ` Johannes Thumshirn
2017-07-14 11:25 ` Johannes Thumshirn
2017-08-15 22:46 ` Guilherme G. Piccoli
2017-08-16 8:16 ` Christoph Hellwig
2017-08-16 16:19 ` Guilherme G. Piccoli
2017-08-28 10:15 ` Guan Junxiong
2017-07-10 8:59 ` Jack Wang
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=20170711085204.GA7846@linux-x5ow.site \
--to=jthumshirn@suse.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.