Hi Ohad,
On 08/13/2014 08:40 AM, Ohad Ben-Cohen wrote:
> Hi Suman,
>
> On Tue, Aug 12, 2014 at 7:19 PM, Suman Anna wrote:
>> Yes, I was playing around with using less buffers in the remoteproc
>> resource table for the vrings. The remoteproc virtio code creates the
>> vrings using the number of
Hi Suman,
On Tue, Aug 12, 2014 at 7:19 PM, Suman Anna wrote:
> Yes, I was playing around with using less buffers in the remoteproc
> resource table for the vrings. The remoteproc virtio code creates the
> vrings using the number of buffers based on .num field value of struct
> fw_rsc_vdev_vring i
Hi Ohad,
On 08/12/2014 10:30 AM, Ohad Ben-Cohen wrote:
> Hi Suman,
>
> On Thu, Jul 3, 2014 at 11:53 PM, Suman Anna wrote:
>> The buffers to be used for communication are allocated during
>> the rpmsg virtio driver's probe, and the number of buffers is
>> currently hard-coded to 512. Remove this
Hi Suman,
On Thu, Jul 3, 2014 at 11:53 PM, Suman Anna wrote:
> The buffers to be used for communication are allocated during
> the rpmsg virtio driver's probe, and the number of buffers is
> currently hard-coded to 512. Remove this hard-coded value, as
> this can vary from one platform to another
The buffers to be used for communication are allocated during
the rpmsg virtio driver's probe, and the number of buffers is
currently hard-coded to 512. Remove this hard-coded value, as
this can vary from one platform to another or between different
remote processors. Instead, rely on the number of