From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Mike Heinz <michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Todd Rimmer <todd.rimmer-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] An argument for allowing applications to manually send RMPP packets if desired
Date: Fri, 16 Sep 2011 21:42:51 -0600 [thread overview]
Message-ID: <20110917034251.GA6056@obsidianresearch.com> (raw)
In-Reply-To: <4C2744E8AD2982428C5BFE523DF8CDCB4A5387ECDF-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
On Fri, Sep 16, 2011 at 01:28:16PM -0500, Mike Heinz wrote:
> The patch at hand avoids all that complexity by simply allowing the SM
> application handle RMPP itself in whatever manner is considered best. If
> the SM wants to use the current RMPP implementation it can, turning this
> ability on is completely optional.
I agree, this is a good idea. Allowing the SM to control the RMPP
entirely, and amortize the content generation across the entire query
is a very good way to manage many of the issues with a RMPP heavy work
load.
Ultimately I think the scalable/compatible answer is to move these
RMPP work loads to a verbs QP and we need to have a user space RMPP
implementation for that anyhow.
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
next prev parent reply other threads:[~2011-09-17 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 16:02 [PATCH] An argument for allowing applications to manually send RMPP packets if desired Mike Heinz
[not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB4A5387E899-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2011-09-12 17:15 ` Roland Dreier
[not found] ` <CAL1RGDUXM9-Ey1aF8xQo3X_L1PLrVyyLPYvqmy6Qeu5M2JnJPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-12 17:23 ` Jason Gunthorpe
[not found] ` <20110912172334.GC18574-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-09-12 18:29 ` Roland Dreier
[not found] ` <CAL1RGDVPZzMKmMg7mokhG0btX+3NH_+tL-9P5guV10h6X6i0iw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-12 18:53 ` Hefty, Sean
2011-09-12 19:06 ` Jason Gunthorpe
[not found] ` <20110912190623.GD18574-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-09-16 18:28 ` Mike Heinz
[not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB4A5387ECDF-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2011-09-17 3:42 ` Jason Gunthorpe [this message]
[not found] ` <20110917034251.GA6056-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-09-19 0:35 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237316E5B763-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-09-19 15:30 ` Mike Heinz
2011-10-24 17:04 ` Mike Heinz
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=20110917034251.GA6056@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
--cc=todd.rimmer-h88ZbnxC6KDQT0dZR+AlfA@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