Hi again Yevgeny,
On Wed, 2007-01-31 at 17:19, Yevgeny Kliteynik wrote:
[snip...]
+ for (i = 0; i IB_MAX_NUM_VLS; i++)
+ {
+ if (valid_sls[i])
+ {
+ vl = ib_slvl_table_get(p_slvl_tbl,i);
+ if (vl == IB_DROP_VL)
Does vl Operational VLs need
Hi Yevgeny,
On Tue, 2007-01-30 at 10:33, Yevgeny Kliteynik wrote:
Checking PathRecord query for QoS constraints
The QoS-aware path selection logic is implemented in a
separate function that is called only when QoS in OpenSM
is on. It causes some code duplication, but the idea is
to
On 17:33 Tue 30 Jan , Yevgeny Kliteynik wrote:
Checking PathRecord query for QoS constraints
The QoS-aware path selection logic is implemented in a
separate function that is called only when QoS in OpenSM
is on. It causes some code duplication, but the idea is
to minimize the changes in
Hi Hal,
Hal Rosenstock wrote:
Hi Yevgeny,
On Tue, 2007-01-30 at 10:33, Yevgeny Kliteynik wrote:
Checking PathRecord query for QoS constraints
The QoS-aware path selection logic is implemented in a
separate function that is called only when QoS in OpenSM
is on. It causes some code
Hi Sasha,
Sasha Khapyorsky wrote:
On 17:33 Tue 30 Jan , Yevgeny Kliteynik wrote:
Checking PathRecord query for QoS constraints
The QoS-aware path selection logic is implemented in a
separate function that is called only when QoS in OpenSM
is on. It causes some code duplication, but the
Checking PathRecord query for QoS constraints
The QoS-aware path selection logic is implemented in a
separate function that is called only when QoS in OpenSM
is on. It causes some code duplication, but the idea is
to minimize the changes in the existing logic in OSM.
Eventually, these two
