From: Roland Dreier <rdreier@cisco.com>
To: "Or Gerlitz" <or.gerlitz@gmail.com>
Cc: "Sean Hefty" <mshefty@ichips.intel.com>,
linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Re: [ofa-general] Further 2.6.23 merge plans...
Date: Tue, 17 Jul 2007 20:23:38 -0700 [thread overview]
Message-ID: <adaabtuo0n9.fsf@cisco.com> (raw)
In-Reply-To: <15ddcffd0707172020j5b68fcb2v7d3ca77863998020@mail.gmail.com> (Or Gerlitz's message of "Wed, 18 Jul 2007 06:20:15 +0300")
> > But to be fair, it will be difficult to enable both QoS and local PR
> > caching. To me, this would be the strongest reason against using it.
> > However, QoS places additional burden on the SA, which will make scaling
> > even more challenging.
>
> my understanding is that the local sa does a path-query where all the fields
> except for the SGID are wildcard-ed. This means we expect the result to be a
> table of all the paths from this port to every other port on the fabrics for
> every pkey which this port is a member of etc, correct?
>
> How do you plug here the QoS concept of SID in the path query? are you
> expecting the SA to realize what are all the services for which this port is
> a "member"? does the proposed definision for QoS management at the SA
> defines "services per gids" isn't it "what SL to user per Service"?
Or, thanks for rescuing this post.
I think this is an important question. If we merge the local SA
stuff, then are we creating a problem for dealing with QoS? Are we
going to have to revert the local SA stuff once the QoS stuff is
available? Or is there at least a sketch of a plan on how to handle
this?
- R.
next prev parent reply other threads:[~2007-07-18 3:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 23:07 [GIT PULL] please pull infiniband.git Roland Dreier
2007-07-12 23:15 ` Further 2.6.23 merge plans Roland Dreier
2007-07-13 0:17 ` [ofa-general] " Hal Rosenstock
2007-07-13 1:14 ` Sean Hefty
[not found] ` <15ddcffd0707172020j5b68fcb2v7d3ca77863998020@mail.gmail.com>
2007-07-18 3:23 ` Roland Dreier [this message]
2007-07-18 5:26 ` Sean Hefty
2007-07-18 17:05 ` Sean Hefty
2007-07-18 20:54 ` Sean Hefty
2007-07-13 5:47 ` Michael S. Tsirkin
2007-07-13 18:14 ` Roland Dreier
2007-07-13 18:50 ` [ofa-general] " Shirley Ma
2007-07-17 18:06 ` Roland Dreier
2007-07-14 17:54 ` Michael S. Tsirkin
[not found] ` <OF72F6B9D1.F60C4EEF-ON8725731A.00506757-8825731A.0024BD1C@us.ibm.com>
2007-07-16 14:55 ` [ofa-general] " Michael S. Tsirkin
2007-07-16 16:42 ` Roland Dreier
2007-07-16 20:05 ` Michael S. Tsirkin
2007-07-17 17:53 ` Roland Dreier
2007-07-13 18:56 ` [ofa-general] " Shirley Ma
2007-07-16 16:47 ` Roland Dreier
2007-07-15 12:26 ` Tziporet Koren
2007-07-16 16:42 ` Roland Dreier
2007-07-17 18:07 ` Roland Dreier
2007-07-17 20:43 ` Matt Leininger
2007-07-17 20:45 ` Roland Dreier
2007-07-18 6:36 ` Or Gerlitz
2007-07-17 21:44 ` Michael S. Tsirkin
2007-07-18 7:34 ` [ofa-general] " Tziporet Koren
2007-07-18 7:38 ` Michael S. Tsirkin
2007-07-18 8:48 ` Tziporet Koren
2007-07-18 16:16 ` Sean Hefty
2007-07-18 16:20 ` Roland Dreier
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=adaabtuo0n9.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshefty@ichips.intel.com \
--cc=or.gerlitz@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).