All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>
Cc: Mike Heinz
	<michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@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: Mon, 12 Sep 2011 11:23:35 -0600	[thread overview]
Message-ID: <20110912172334.GC18574@obsidianresearch.com> (raw)
In-Reply-To: <CAL1RGDUXM9-Ey1aF8xQo3X_L1PLrVyyLPYvqmy6Qeu5M2JnJPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Mon, Sep 12, 2011 at 10:15:08AM -0700, Roland Dreier wrote:
> > But is this really needed? Consider that these 3,000 replies only
> > differ in their destination addresses - the actual data is
> > identical in all of them.  Moreover, the data returned for a query
> > like this changes only rarely in a production fabric - which means
> > that the response could be generated once and then and then
> > re-used to provide responses to multiple clients.
> >
> > To allow this, however, the SM must be allowed to explicitly
> > manage its own RMPP transmissions instead of sending each response
> > as a complete unit. If this is allowed, then the kernel no longer
> > needs to allocate large amounts of buffer space, and the SM can
> > build the results of certain queries in advance, updating them
> > only when the fabric changes, instead of recreating them each time
> > it receives an IB_MAD_METHOD_GET_TABLE.
> 
> It seems at least the SM side could be handled using writev() to
> splice together the data it wants to send.

How does that help avoid the kernel memory allocations?

I think having the option for RMPP in user space is a good idea, it
allows much more efficiency on the SM side..

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

  parent reply	other threads:[~2011-09-12 17:23 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 [this message]
     [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
     [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=20110912172334.GC18574@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 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.