Hi,
>
> spinlock intent_lock initialization is missed ?
right, should add that.
>> kref_init(&channel->refcount);
>> return channel;
>> @@ -187,6 +215,7 @@ static void qcom_glink_channel_release(struct kref *ref)
>> struct glink_channel *channel = container_of(ref, struct
On 8/16/2017 10:49 PM, Sricharan R wrote:
Intents are nothing but pre-allocated buffers of
appropriate size that are allocated on the local
side and communicated to the remote side and the
remote stores the list of intent ids that it is
informed.
Later when remote side is intenting to send dat
Intents are nothing but pre-allocated buffers of
appropriate size that are allocated on the local
side and communicated to the remote side and the
remote stores the list of intent ids that it is
informed.
Later when remote side is intenting to send data,
it picks up a right intent (based on the si
3 matches
Mail list logo
