Re: multiple tcp connections

[hufferd@us.ibm.com]

Julian,
Since a session is only an iSCSI thing, your statements would be correct
even if there were only one TCP connection per session, but several
sessions on the same NIC.




.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSD San Jose Ca
(408) 256-0403, Tie: 276-0403
Internet address: hufferd@us.ibm.com
Notes address: John Hufferd/San Jose/IBM @ IBMUS
VM address: hufferd at IBMUSM54


Julian Satran/Haifa/IBM@IBMIL@ece.cmu.edu on 07/07/2000 11:18:48 PM

Sent by:  owner-ips@ece.cmu.edu


To:   ips@ece.cmu.edu
cc:
Subject:  Re: multiple tcp connections





Parallelism on end-points could be another reasons.

A long time ago when running some benchmarks we achieved considerably
better numbers with 4 sockets than with one.

This type of result repeated itself in different contexts and with
different stacks.

That is probably due to some serialization that is inherent in the way
stacks are built
and API's are used (this is a long discussion subject).

With SMPs the differences are even more striking.

Julo

Matt Wakeley <matt_wakeley@agilent.com> on 08/07/2000 02:11:57

Please respond to Matt Wakeley <matt_wakeley@agilent.com>

To:   Randy Haagens <Randy_Haagens@hp.com>, Julian Satran/Haifa/IBM@IBMIL
cc:
Subject:  multiple tcp connections




Hi,

I was asked the question:

If there is only 1 MAC (available to the system), would there ever be more
than 1 tcp connection per iSCSI session.  I couldn't think of a good reason
why there would be, but thought I'd ask you. The only reason I could think
of
using multiple tcp connections per iSCSI session was for port aggregation
when
there are multiple MACs available.  Any comments?

Thanks,

-Matt