All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Paul Grun <pgrun-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
Cc: 'Bang Nguyen'
	<bang.nguyen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	'Richard Frank'
	<richard.frank-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: APM support for IPoIB
Date: Tue, 2 Oct 2012 11:00:08 -0600	[thread overview]
Message-ID: <20121002170008.GA23733@obsidianresearch.com> (raw)
In-Reply-To: <009101cda0be$6d8cb220$48a61660$@com>

On Tue, Oct 02, 2012 at 09:53:17AM -0700, Paul Grun wrote:

> Jason - Like your idea for full APM support especially across
> subnets, but wouldn't that require some sort capability that lives
> above the subnet level and is able to query both SMs/SAs?  Sounds
> vaguely router-ish?

Well, in terms of the current spec, PRs are fully specified enough
that a sufficiently informed SA can return PRs for a non-requesting
port on the same node. I've long advocated for an improved PR
mechanism that would be more APM 'aware' and router compatible
(Connected Path Query)

There are a few good ways to get that sort of information into the
SA..

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

  reply	other threads:[~2012-10-02 17:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 22:23 APM support for IPoIB Bang Nguyen
     [not found] ` <506A17EA.8080400-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2012-10-01 23:53   ` Jason Gunthorpe
     [not found]     ` <20121001235303.GH22342-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-10-02  0:02       ` Bang Nguyen
     [not found]         ` <506A2F01.8000605-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2012-10-02  2:15           ` Roland Dreier
     [not found]             ` <CAL1RGDWmywbGg0vVb_MqRCHbdgMCZTGN5Y-dX6NkpWRB6P23ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-02  8:12               ` Tziporet Koren
     [not found]                 ` <CD250C48050CFB4D95E78C95F2FDDD6E87470513-fViJhHBwANKuSA5JZHE7gA@public.gmane.org>
2012-10-03  0:14                   ` Bang Nguyen
     [not found]                     ` <506B8365.9010507-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2012-10-03  3:03                       ` Hefty, Sean
     [not found]                         ` <1828884A29C6694DAF28B7E6B8A8237346A98B11-Q3cL8pyY+6ukrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-10-03  4:24                           ` Bang Nguyen
     [not found]                             ` <506BBDE3.3010904-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2012-10-04 16:06                               ` Bang Nguyen
2012-10-02 16:53       ` Paul Grun
2012-10-02 17:00         ` Jason Gunthorpe [this message]
2012-10-02 17:21         ` Hefty, Sean

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=20121002170008.GA23733@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=bang.nguyen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pgrun-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org \
    --cc=richard.frank-QHcLZuEGTsvQT0dZR+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.