From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: Sagi Grimberg <sagig@mellanox.com>
Cc: Bart Van Assche <bvanassche@acm.org>, Vu Pham <vu@mellanox.com>,
lsf-pc@lists.linux-foundation.org,
linux-scsi <linux-scsi@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
David Dillow <dillowda@ornl.gov>, Oren Duer <oren@mellanox.com>
Subject: Re: [LSF/MM TOPIC] Reducing the SRP initiator failover time
Date: Fri, 08 Feb 2013 12:38:46 +0100 [thread overview]
Message-ID: <5114E3C6.9010900@profitbricks.com> (raw)
In-Reply-To: <5114C453.7010904@mellanox.com>
On 08.02.2013 10:24, Sagi Grimberg wrote:
> On 2/8/2013 12:42 AM, Vu Pham wrote:
>> Hello Bart,
>>
>> Thank you for taking the initiative.
>> Mellanox think that this should be discussed. We'd be happy to attend.
>>
>> We also would like to discuss:
>> * How and how fast does SRP detect a path failure besides RC error?
>> * Role of srp_daemon, how often srp_daemon scan fabric for new/old
>> targets, how-to scale srp_daemon discovery, traps.
>>
>> -vu
> Hey Bart,
>
> I agree with Vu that this issue should be discussed. We'd be happy to
> attend.
>
> --
> Sagi
Wow, also thanks to Mellanox for spending resources on SRP as well! Last
year in June we came across a very different situation.
Cheers,
Sebastian and the ProfitBricks storage team
prev parent reply other threads:[~2013-02-08 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 13:43 [LSF/MM TOPIC] Reducing the SRP initiator failover time Bart Van Assche
[not found] ` <510BC68A.90708-HInyCGIudOg@public.gmane.org>
2013-02-04 12:13 ` Sebastian Riemer
[not found] ` <CAJZOPZJeCdkJ0xfK0kxic9jfz5A5ddw7TSWXe51yuO6bYTk4ag@mail.gmail.com>
[not found] ` <BB97625FCF082447AC2B11418FF02044A6E9E9C5@MTLDAG01.mtl.com>
[not found] ` <BB97625FCF082447AC2B11418FF02044A6E9E9C5-fViJhHBwANKuSA5JZHE7gA@public.gmane.org>
2013-02-07 22:42 ` Vu Pham
[not found] ` <51142DE9.30900-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-02-08 9:24 ` Sagi Grimberg
2013-02-08 11:38 ` Sebastian Riemer [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=5114E3C6.9010900@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=bvanassche@acm.org \
--cc=dillowda@ornl.gov \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=oren@mellanox.com \
--cc=sagig@mellanox.com \
--cc=vu@mellanox.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).