linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	Dave Gerlach <d-gerlach@ti.com>
Subject: Re: [PATCHv2] rpmsg: compute number of buffers to allocate from vrings
Date: Thu, 13 Nov 2014 11:46:04 -0600	[thread overview]
Message-ID: <5464EE5C.8090904@ti.com> (raw)
In-Reply-To: <1410892387-30596-1-git-send-email-s-anna@ti.com>

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 <s-anna@ti.com>
> ---
> 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

  reply	other threads:[~2014-11-13 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 18:33 [PATCHv2] rpmsg: compute number of buffers to allocate from vrings Suman Anna
2014-11-13 17:46 ` Suman Anna [this message]
2014-11-26 16:52   ` Ohad Ben-Cohen
2014-11-26 22:30     ` Suman Anna
2014-11-28 15:18       ` Ohad Ben-Cohen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5464EE5C.8090904@ti.com \
    --to=s-anna@ti.com \
    --cc=d-gerlach@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).