From: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Gil Rockah <gilr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Subject: Re: [PATCH perftest] perftest: make inline send on ocrdma work better
Date: Fri, 19 Aug 2016 17:12:42 -0400 [thread overview]
Message-ID: <20160819211242.GY1916@redhat.com> (raw)
In-Reply-To: <85f0801f-a78f-7091-7ae2-5febde6b19b6-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
On Fri, Aug 19, 2016 at 03:45:57PM -0500, Steve Wise wrote:
> On 8/19/2016 2:06 PM, Jarod Wilson wrote:
> >The ocrdma driver supports a maximum inline send size of 224, while the
> >current code sets this size to 236. Add an ocrdma-specific check when
> >setting max inline size to eliminate the need to always pass -I 224 when
> >running ib_send_lat on ocrdma hardware.
>
> <soap box>
> We really should fix the RDMA uAPI to allow querying the device to
> get the max inline size for various SQ WRs (it might vary for send
> vs write, for example), instead of requiring applications to guess
> or hardcoding benchmarks based on device name...
> </soap box>
This was a nice quick hack Friday afternoon hack to get it working
with existing kernels in our testing infra, but having a way to ask
the hardware would definitely be vastly superior.
--
Jarod Wilson
jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
--
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:[~2016-08-19 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 19:06 [PATCH perftest] perftest: make inline send on ocrdma work better Jarod Wilson
[not found] ` <1471633611-41155-1-git-send-email-jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-08-19 20:45 ` Steve Wise
[not found] ` <85f0801f-a78f-7091-7ae2-5febde6b19b6-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2016-08-19 21:12 ` Jarod Wilson [this message]
[not found] ` <20160819211242.GY1916-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-08-19 21:31 ` Steve Wise
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=20160819211242.GY1916@redhat.com \
--to=jarod-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=gilr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@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.