From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suman Anna Subject: Re: [PATCHv2] rpmsg: compute number of buffers to allocate from vrings Date: Thu, 13 Nov 2014 11:46:04 -0600 Message-ID: <5464EE5C.8090904@ti.com> References: <1410892387-30596-1-git-send-email-s-anna@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1410892387-30596-1-git-send-email-s-anna@ti.com> Sender: linux-kernel-owner@vger.kernel.org To: Ohad Ben-Cohen Cc: Rusty Russell , linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Dave Gerlach List-Id: linux-omap@vger.kernel.org Hi Ohad, On 09/16/2014 01:33 PM, Suman Anna wrote: > The buffers to be used for communication are allocated during the > rpmsg virtio driver's probe, and the total number of buffers is > currently hard-coded to 512. The vring configuration can vary from > one platform to another or between different remote processors. The > setup of the receive buffers will throw a WARN_ON if the associated > vrings are configured with less than 256 buffers (in each direction). > So, adjust this hard-coded value to rely on the number of buffers the > virtqueue vring is setup with, but also limit to use 256 buffers at > most in each direction to avoid wacky resource tables consuming up > unreasonable memory. > > NOTE: The number of buffers is already assumed to be symmetrical > in each direction, and that logic is not unchanged. > > Signed-off-by: Suman Anna > --- > v2 changes: > - add upper limit on buffers and update comments > - revise patch description Any comments on this one, if not can you pick this up for 3.19? regards Suman