Hi Sasha,
Please see my comments below
9. OpenSM features
---
The QoS related functionality to be provided by OpenSM can be split
into two
main parts:
3.1. Fabric Setup
During fabric initialization the SM should parse the policy and
apply its
settings to the
On 15:49 Tue 30 May , Grant Grundler wrote:
On Tue, May 30, 2006 at 10:09:36PM +0300, Sasha Khapyorsky wrote:
XML style syntax is provided for the policy file.
Why XML? It is not too much readable and writable (by human) format.
It is human readable and very portable.
An example
Hi Eitan,
Some more comments related to OpenSM.
On 17:53 Tue 30 May , Eitan Zahavi wrote:
9. OpenSM features
---
The QoS related functionality to be provided by OpenSM can be split into two
main parts:
3.1. Fabric Setup
During fabric initialization the SM should
On Thu, Jun 01, 2006 at 09:09:49PM +0300, Sasha Khapyorsky wrote:
On 15:49 Tue 30 May , Grant Grundler wrote:
On Tue, May 30, 2006 at 10:09:36PM +0300, Sasha Khapyorsky wrote:
XML style syntax is provided for the policy file.
Why XML? It is not too much readable and writable (by
: RE: [openib-general] QoS RFC - Resend using a friendly mailer
Hi Todd,
It is LWG. MgtWG will also be involved.
I am a member of IBTA however I have not noticed this discussion on
the IBTA
working groups. Which working group have you engaged with this
proposal?
Todd Rimmer
To: OPENIB openib-general@openib.org
Subject: QoS RFC - Resend using a friendly mailer
--text follows this line--
Hi All
Please find the attached RFC describing how QoS policy support could be
implemented in the OpenFabrics stack.
Your comments are welcome.
Eitan
RFC:
Eitan wrote:
2.2. The SM analyzes the provided policy to see if it is
realizable and performs
the necessary fabric setup. The SM may continuously monitor
the policy and adapt
to changes in it. Part of this policy defines the default
QoS-Level of each
partition. The SA is being
On Tue, 2006-05-30 at 10:53, Eitan Zahavi wrote:
To: OPENIB openib-general@openib.org
Subject: QoS RFC - Resend using a friendly mailer
--text follows this line--
Hi All
Please find the attached RFC describing how QoS policy support could be
implemented in the OpenFabrics stack.
Your
High-level feedback:
- An IB fabric could be used for a single ULP and still require
QoS. The issue is how to differentiate flows on a given shared
element within the fabric.
- QoS controls must be dynamic. The document references initialization as
the time when decisions are made but obviously
Hi Eitan,
First comments...
On 17:53 Tue 30 May , Eitan Zahavi wrote:
3. Supported Policy
The QoS policy supported by this proposal is divided into 4 sub sections:
* Node Group: a set of HCAs, Routers or Switches that share the same
settings.
A node groups
Hi Todd,
While using the Service ID is an interesting idea, the problem is the
Service ID values
are not well defined by IBTA. Rather each endpoint is permitted to
define its own,
potentially transient set of Service ID values. The Service ID values
are discovered via
Service Records in
Hi Hal,
Please see my responses inside
Eitan
RFC: OpenFabrics Enhancements for QoS Support
===
Authors: . Eitan Zahavi [EMAIL PROTECTED]
Date: May 2006.
Revision: 0.1
Table of contents:
1. Overview
Hi Sasha,
Thanks for your comments.
Please see my comments inside
3. Supported Policy
The QoS policy supported by this proposal is divided into 4 sub
sections:
* Node Group: a set of HCAs, Routers or Switches that share the same
settings.
A node groups might be
On 22:43 Tue 30 May , Eitan Zahavi wrote:
XML style syntax is provided for the policy file.
Why XML? It is not too much readable and writable (by human) format.
[EZ] Well, I agree with you but already got so many requests for XML
that I could not resists. Maybe we could do both.
Eitan Wrote:
As Roland suggest, before implementing a non-standard approach, IBTA
should be
engaged to define an appropriate extension to the standard. Such
extensions would
need to be carefully defined to avoid breaking existing applications
and fabrics.
[EZ] You are welcome to join
On Tue, 2006-05-30 at 18:05, Rimmer, Todd wrote:
Eitan Wrote:
As Roland suggest, before implementing a non-standard approach, IBTA
should be
engaged to define an appropriate extension to the standard. Such
extensions would
need to be carefully defined to avoid breaking existing
Hi Todd,
It is LWG. MgtWG will also be involved.
I am a member of IBTA however I have not noticed this discussion on
the IBTA
working groups. Which working group have you engaged with this
proposal?
Todd Rimmer
___
openib-general mailing list
17 matches
Mail list logo