From: Muneendra Kumar M <muneendra.kumar@broadcom.com>
To: Hannes Reinecke <hare@suse.de>,
Martin Wilck <martin.wilck@suse.com>,
erwin@erwinvanlonden.net, bblock@linux.ibm.com
Cc: dm-devel@redhat.com
Subject: Re: [dm-devel] dm-multipath - IO queue dispatch based on FPIN Congestion/Latency notifications.
Date: Wed, 31 Mar 2021 17:27:35 +0530 [thread overview]
Message-ID: <c661804f254c8dec17b57c6b95f0fe05@mail.gmail.com> (raw)
In-Reply-To: <0419387c-071c-2c5e-79f4-8873553e5da3@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1485 bytes --]
Hi Martin,
>>
>> I'm aware of Ben's work, but I hadn't realized it had anything to do
>> with FPIN. As of today, multipathd doesn't listen on the
>> NETLINK_SCSITRANSPORT socket. Does any user space tool do this?
> >Google didn't show me anything.
> >
>I did, once, but that was years ago.
We have user space daemon(Broadcom'sFiber Channel Transport Daemon) called
fctxpd (Benjamin was talking in his patch) which acts on fpin-li events
by listening on NETLINK_SCSITRANSPORT socket
And it sets the path to marginal path group on receiving FPIN events.
This daemon is part of epel8.
Below is the path for the same where we have changes
https://github.com/brocade/bsn-fc-txptd
Regards,
Muneendra.
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4220 bytes --]
[-- Attachment #2: Type: text/plain, Size: 97 bytes --]
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-03-31 13:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 7:52 [dm-devel] dm-multipath - IO queue dispatch based on FPIN Congestion/Latency notifications Erwin van Londen
2021-03-25 16:07 ` Benjamin Block
2021-03-26 11:15 ` Muneendra Kumar M
2021-03-31 0:22 ` Erwin van Londen
2021-03-31 7:25 ` Hannes Reinecke
2021-03-31 8:12 ` Erwin van Londen
2021-03-31 9:57 ` Martin Wilck
2021-03-31 10:48 ` Muneendra Kumar M
2021-03-31 11:45 ` Martin Wilck
2021-03-31 11:53 ` Hannes Reinecke
2021-03-31 11:57 ` Muneendra Kumar M [this message]
2021-03-31 12:41 ` Martin Wilck
2021-04-01 2:48 ` Erwin van Londen
2021-04-01 10:16 ` Martin Wilck
2021-04-01 22:04 ` Erwin van Londen
2021-04-05 5:30 ` Muneendra Kumar M
2021-04-05 5:55 ` Erwin van Londen
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=c661804f254c8dec17b57c6b95f0fe05@mail.gmail.com \
--to=muneendra.kumar@broadcom.com \
--cc=bblock@linux.ibm.com \
--cc=dm-devel@redhat.com \
--cc=erwin@erwinvanlonden.net \
--cc=hare@suse.de \
--cc=martin.wilck@suse.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 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.