Sean Hefty wrote:
And as you've mentioned, some rules may overlap. For instance,
if the rule for all the RDS traffic will appear before the iSER
rule, then iSER requests will be caught by the RDS rule.
That doesn't sound so good but I don't see a good alternative here other
than for this case to put the iSER rule first. The other fallback is the
more detailed configuration but RDS falls into the generic range
category which is problematic in terms of this (and can't be
differentiated by ServiceID unlike the other ULPs).
I'm not overly familiar with the details of RDS, but event if the active side
uses a dynamic service ID, I would expect the passive side to use something well
known.
Couldn't agree more.
That's why I think that although there are cases where this simplified
way of defining SLs per ULP plus target TCP port won't be useful, in
many cases it would actually make the administrator's life easier.
-- Yevgeny
- Sean
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
