RE: Patches for fine-grained rsocket preloading

[Sreedhar Kodali <srkodali-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>]

On 2014-09-04 23:45, Hefty, Sean wrote:
>> I didn't follow this.  If rsocket is behaving differently than normal
>> sockets, I'm fine updating it so that it matches the desired behavior. 
>>  It
>> doesn't need to be an option.
>> 
>> That said, can you provide more details on what the desired behavior
>> should be and what rsockets is doing differently?
> 
> I did a quick test, and I *think* the difference that you're referring
> to is this:
> 
> Normal sockets:
> listen(sX) -> returns success
> listen(sX) -> returns success
> 
> rsockets
> rlisten(rsY) -> returns success
> rlisten(rsY) -> fails
> 
> Can you confirm that this is the problem you want to address?
> 
> If so, then I think a fix to rsockets is needed, rather than trapping
> this in the preload library.
> 
> - Sean

Hi Sean,

Yes, that's right.
However, one minor correction - even though my fix is not appropriate
as I have found later, it was still part of rsockets code only.  Since,
I have combined all the patches together perhaps it might have confused 
you.

Thank You.

- Sreedhar

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html