All of lore.kernel.org
 help / color / mirror / Atom feed
From: Panu Matilainen <pmatilai@redhat.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2] examples/vhost: reduce number of hugepages needed
Date: Fri, 11 Dec 2015 11:05:13 +0200	[thread overview]
Message-ID: <566A91C9.5040500@redhat.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836AD25A2@irsmsx105.ger.corp.intel.com>

On 12/10/2015 04:50 PM, Ananyev, Konstantin wrote:
>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bernard Iremonger
>> Sent: Thursday, December 10, 2015 1:53 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] [PATCH v2] examples/vhost: reduce number of hugepages needed
>>
>> Change MAX_QUEUES from 512 to 128 to reduce the number of hugepages
>> required by the vhost-switch program.
>>
>> Changes in v2:
>> remove comment added before #define MAX_QUEUES in v1 patch.
>>
>> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
>> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
>
>
> Wasn't it increased a while ago, because someone complained that
> 128 queues might not be enough on FVL?
>  From git log I can see that it was first increased from 128 to 256,
> then from 256 to 512.
> The reason mentioned - HW that has bigger number of queues.
> Isn't it not the case anymore?
> If yes, why?
>
> BTW, shouldn't it be then at least:
>
> +#ifndef MAX_QUEUES
> +#define MAX_QUEUES 128
> +#endif
>
> So people can just do -D MAX_QUEUES=X at build time if they like(need) to.

Being subject to constant changes back and forth suggests this really 
should be a runtime tunable rather than build time constant.

	- Panu -

  parent reply	other threads:[~2015-12-11  9:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 12:19 [PATCH] examples/vhost: reduce number of hugepages needed Bernard Iremonger
2015-12-10 12:59 ` Yuanhan Liu
2015-12-10 13:26   ` Iremonger, Bernard
2015-12-10 13:34     ` Yuanhan Liu
2015-12-10 13:53 ` [PATCH v2] " Bernard Iremonger
2015-12-10 14:50   ` Ananyev, Konstantin
2015-12-10 15:43     ` Iremonger, Bernard
2015-12-11  9:05     ` Panu Matilainen [this message]
2015-12-10 15:49   ` [PATCH v3] " Bernard Iremonger
2015-12-10 16:32     ` Ananyev, Konstantin
2015-12-10 21:35       ` Thomas Monjalon

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=566A91C9.5040500@redhat.com \
    --to=pmatilai@redhat.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.