From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH rdma-core 0/2] Flow steering handling
Date: Thu, 9 Nov 2017 10:53:47 -0700 [thread overview]
Message-ID: <20171109175347.GL7063@ziepe.ca> (raw)
In-Reply-To: <1510157897-10384-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Wed, Nov 08, 2017 at 06:18:15PM +0200, Yishai Hadas wrote:
> This series aligns in the user space area the flow steering uverbs commands
> with other objects (e.g. QP, CQ) such that the commands don't allocate and free
> the ib_flow but are just responsible to issue the command.
>
> The second patch in the series in mlx4 handles the cleanup on fatal scenario as
> already done for other destroy commands on top of the above change.
>
> PR was sent:
> https://github.com/linux-rdma/rdma-core/pull/244
Reviewed-by: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Jason
--
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
prev parent reply other threads:[~2017-11-09 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 16:18 [PATCH rdma-core 0/2] Flow steering handling Yishai Hadas
[not found] ` <1510157897-10384-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-08 16:18 ` [PATCH rdma-core 1/2] Align flow steering commands with other objects Yishai Hadas
2017-11-08 16:18 ` [PATCH rdma-core 2/2] mlx4: Cleanup upon fatal in the destroy flow Yishai Hadas
2017-11-09 13:30 ` [PATCH rdma-core 0/2] Flow steering handling Yishai Hadas
2017-11-09 17:53 ` Jason Gunthorpe [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=20171109175347.GL7063@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@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 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.