Kanevsky, Arkady wrote:
Exactly, it forces the burden on administrator. And one will be forced to try one mount for iWARP and it does not work issue another one TCP or UDP if it fails. Yack!
I see your point. I have no defense. My hands have been tied on fixing this properly...
And server will need to listen on different IP address and simple * will not work since it will need to listen in two different domains.
No, the server will listen on 0.0.0.0:2049 for TCP, and 0.0.0.0:2050 for rdma. The rdma subsystem will translate 0.0.0.0:2050 into listens on specific iwarp ip addresses on every iwarp device...
Had we run this proposal by administrators?
There has been no other solution proposed that Dave Miller and Jeff Garzik won't NAK...
Steve. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH v3] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- From: Steve Wise <[email protected]>
- Re: [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- From: Sean Hefty <[email protected]>
- RE: [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only" interfacesto avoid 4-tuple conflicts.
- From: "Kanevsky, Arkady" <[email protected]>
- RE: [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only"interfacesto avoid 4-tuple conflicts.
- From: "Sean Hefty" <[email protected]>
- RE: [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid 4-tuple conflicts.
- From: "Kanevsky, Arkady" <[email protected]>
- Re: [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid 4-tuple conflicts.
- From: Steve Wise <[email protected]>
- RE: [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid 4-tuple conflicts.
- From: "Kanevsky, Arkady" <[email protected]>
- [PATCH v3] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- Prev by Date: Re: [patch 0/2] suspend/resume regression fixes
- Next by Date: Re: PATCH: tcp rfc 2385 security/bugfix for sparc64
- Previous by thread: RE: [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid 4-tuple conflicts.
- Next by thread: Re: [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid 4-tuple conflicts.
- Index(es):
 |