Re: Integration of SCST in the mainstream Linux kernel



On Tue, 2008-02-05 at 14:12 -0500, Jeff Garzik wrote:
Vladislav Bolkhovitin wrote:
Jeff Garzik wrote:
iSCSI is way, way too complicated.

I fully agree. From one side, all that complexity is unavoidable for
case of multiple connections per session, but for the regular case of
one connection per session it must be a lot simpler.


Actually, think about those multiple connections... we already had to
implement fast-failover (and load bal) SCSI multi-pathing at a higher
level. IMO that portion of the protocol is redundant: You need the
same capability elsewhere in the OS _anyway_, if you are to support
multi-pathing.

Jeff



Hey Jeff,

I put a whitepaper on the LIO cluster recently about this topic.. It is
from a few years ago but the datapoints are very relevant.

http://linux-iscsi.org/builds/user/nab/Inter.vs.OuterNexus.Multiplexing.pdf

The key advantage to MC/S and ERL=2 has always been that they are
completely OS independent. They are designed to work together and
actually benefit from one another.

They are also are protocol independent between Traditional iSCSI and
iSER.

--nab

PS: A great thanks for my former colleague Edward Cheng for putting this
together.




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: Integration of SCST in the mainstream Linux kernel
    ... From one side, all that complexity is unavoidable for case of multiple connections per session, but for the regular case of one connection per session it must be a lot simpler. ... we already had to implement fast-failover SCSI multi-pathing at a higher level. ...
    (Linux-Kernel)
  • Re: Integration of SCST in the mainstream Linux kernel
    ... From one side, all that complexity is unavoidable for case of multiple connections per session, but for the regular case of one connection per session it must be a lot simpler. ... we already had to implement fast-failover SCSI multi-pathing at a higher level. ...
    (Linux-Kernel)
  • Cisco IOS IPS issue
    ... connecting to an MPLS cloud with about 40 sites and on my Gi0/1 port I ... After enabling IPS on the Gi0/0 outbound interface, ... session thresholds are well below max connection limits. ... max-incomplete tcp connections per host is 100000. ...
    (comp.dcom.sys.cisco)
  • Re: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts
    ... Sorry, Russ, but the /console switch only connects if the server ... I log on to my own session in the server, from another workstation, ... Once at the remote site, I figure I need access to some data that I ... connections limit (whenever you're able to connect with an already ...
    (microsoft.public.windows.server.sbs)
  • Re: Concurrent connections for PIX
    ... > I'm aware that there can be multiple connections on a single website. ... I did not get a chance to measure & observe the problem, as the campus ... The other issue we had is with UDP. ... of a UDP 'session' is with simple timers. ...
    (comp.security.firewalls)

Loading