[ofa-general] RE: QoS for iSER

[Hal Rosenstock]

Or,

On 11/13/07, Or Gerlitz <ogerlitz at voltaire.com> wrote:
> Yevgeny,
>
> iSER (as you can learn from doing a grep) is using the RDMA-CM TCP port
> space as does RDS. The RDMA-CM signature is something which I am sure
> exists, you can look on the RDMA-CM IB spec Annex to see if such thing
> indeed exist or I am wrong.

Did you really look at the annex for this ?

> The TCP port is the 16 bit port portion of
> the
> ip:port address provided by a ULP that uses the RDMA-CM to
> rdma_resolve_addr(), again the annex explained how the port is embedded
> into the SID, I don't remember the location within the 64 bit string.

It's in the low 16 bits (bytes 6-7) of the SID as the annex indicates.

> Or.
>
> -------- Original Message --------
> Subject:
> Re: QoS for iSER
> Date:
> Mon, 12 Nov 2007 11:41:43 +0200
> From: Yevgeny Kliteynik <kliteyn at dev.mellanox.co.il>
>
> Hi Erez,
>
> Erez Zilber wrote:
> > to create the SID, the rdma cm combines
> >
> > 1)       the port space
>
> What is the port space for iSER?
> For SDP it's 0x10000 - 0x1FFFF.
> For RDS it's 0x1060000 - 0x106FFFF
> For iSER it's ...?

These numbers are too large for just "port space".

iSER SID is 0x000000000106035c

in your nomenclature, I guess 0x106035c

01 says RDMA aware ULP service ID range
06 says IP protocol is TCP
0x035c (port 860) is the well known TCP port for iSCSI

-- Hal

> > 2)       the rdma cm signature
>
> Do you mean something iSER-specific, or just the way the cm
> builds the service ID out of port space and tcp port?
> Can you give an example?
>
> > 3)       the destination tcp port provided to rdma_resolve_addr
>
> I guess that tcp port is in the lower 4 nibs of the service ID,
> similar to SDP. Right?
> -- Yevgeny
>
> _______________________________________________
> general mailing list
> general at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
>
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
>