From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Shawn Bohrer <shawn.bohrer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hadarh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH V3 for-next 0/4] Add receive Flow Steering support
Date: Tue, 6 Aug 2013 16:11:41 +0300 [thread overview]
Message-ID: <5200F60D.8060500@mellanox.com> (raw)
In-Reply-To: <20130805205437.GA7488-/vebjAlq/uFE7V8Yqttd03bhEEblAqRIDbRjUBewulXQT0dZR+AlfA@public.gmane.org>
On 05/08/2013 23:54, Shawn Bohrer wrote:
> The problem with running and testing this code is that many of these
> features are posted in incomplete (from the user point of view)
> chunks. As an example I don't really see how anyone is currently
> using raw QPs on upstream code since this flow steering patch set is
> missing, I still haven't seen the corresponding patches to libibverbs,
> and IP checksum support is still missing from the send side.
Hi Shawn,
Its common for features to be submitted in bottom/up manner, that is 1st
the kernel part with the API to user space and only later the user space
implementation.
Still, your input and testing is very much valuable, I will send you
user space
patches for libmlx4 and libibverbs so you can test the kernel patches.
Or.
--
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:[~2013-08-06 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 17:42 [PATCH V3 for-next 0/4] Add receive Flow Steering support Or Gerlitz
[not found] ` <1372873336-13694-1-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-03 17:42 ` [PATCH V3 for-next 1/4] IB/core: " Or Gerlitz
2013-07-03 17:42 ` [PATCH V3 for-next 2/4] IB/core: Infra-structure to support verbs extensions through uverbs Or Gerlitz
2013-07-03 17:42 ` [PATCH V3 for-next 3/4] IB/core: Export ib_create/destroy_flow " Or Gerlitz
[not found] ` <1372873336-13694-4-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-17 23:31 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373805B9484-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-07-18 14:47 ` Matan Barak
[not found] ` <51E8001B.5000506-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-18 17:06 ` Hefty, Sean
2013-07-03 17:42 ` [PATCH V3 for-next 4/4] IB/mlx4: Add receive Flow Steering support Or Gerlitz
2013-08-05 20:54 ` [PATCH V3 for-next 0/4] " Shawn Bohrer
[not found] ` <20130805205437.GA7488-/vebjAlq/uFE7V8Yqttd03bhEEblAqRIDbRjUBewulXQT0dZR+AlfA@public.gmane.org>
2013-08-06 13:11 ` Or Gerlitz [this message]
[not found] ` <5200F60D.8060500-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-10 21:53 ` Upinder Malhi (umalhi)
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=5200F60D.8060500@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=hadarh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=shawn.bohrer-Re5JQEeQqe8AvxtiuMwx3w@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