From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Tatyana Nikolova'
<Tatyana.E.Nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
'Doug Ledford' <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: john.s.lacombe-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH for-4.2 0/1] RDMA/core: Fixes for port mapper client registration
Date: Mon, 6 Jul 2015 12:20:33 -0500 [thread overview]
Message-ID: <003301d0b810$10b02070$32106150$@opengridcomputing.com> (raw)
In-Reply-To: <20150702174609.GA11108@TENIKOLO-MOBL2>
> -----Original Message-----
> From: Tatyana Nikolova [mailto:Tatyana.E.Nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org]
> Sent: Thursday, July 02, 2015 12:46 PM
> To: Doug Ledford
> Cc: john.s.lacombe-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org; swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org; linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Subject: [PATCH for-4.2 0/1] RDMA/core: Fixes for port mapper client registration
>
> This patch has been reworked, but is very similar to the previously
> submitted (10/16/2014) patch, which was forgotten:
>
> [PATCH 1/1] RDMA/core: Fixes for port mapper client registration
> https://www.mail-archive.com/linux-rdma%40vger.kernel.org/msg21512.html
>
> This patch is addressing the same issue as the previous one -
> the clients which have provided their mapping info
> to the user space service after it is restarted, are treated as
> unregistered and are not allowed to make remove mapping requests.
>
> If the user space port mapper service is restarted, it notifies
> the port mapper clients and they provide the mapping information they
> have in use. At this time with the fix the registration type of the client
> is set to IWPM_REG_INCOMPL and the client is allowed to make remove
> mapping requests to the user space service.
>
> There are some improvements in the current patch:
> 1) Adding functions to set/check registration type
> 2) New clients (calling iwpm_init()) have their registration set to IWPM_REG_UNDEF
> 3) If the port mapper user space service is not available, then the client
> registration stays IWPM_REG_UNDEF and the registration type won't be
> checked until the service becomes available (obviously no mappings are
> possible, if the user space service isn't running).
>
> For these changes to take effect no provider changes are necessary.
> The patch contains fixes for the current registration logic.
>
Hey Tatyana, how can I reproduce the original bug/issue and then test this fix on iw_cxgb4?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-06 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 17:46 [PATCH for-4.2 0/1] RDMA/core: Fixes for port mapper client registration Tatyana Nikolova
2015-07-06 17:20 ` Steve Wise [this message]
2015-07-06 20:59 ` Nikolova, Tatyana E
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='003301d0b810$10b02070$32106150$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=Tatyana.E.Nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=john.s.lacombe-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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