* [dpdk-dev] Query on portmask config
@ 2015-02-15 2:45 Shankari Vaidyalingam
2015-02-16 10:01 ` De Lara Guarch, Pablo
0 siblings, 1 reply; 2+ messages in thread
From: Shankari Vaidyalingam @ 2015-02-15 2:45 UTC (permalink / raw)
To: dev
Hi,
I'm new to DPDK.
Would like to know how to determine the portmask for a given configuration.
Does it depend on the number of cores configured
Regards
Shankari.V
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] Query on portmask config
2015-02-15 2:45 [dpdk-dev] Query on portmask config Shankari Vaidyalingam
@ 2015-02-16 10:01 ` De Lara Guarch, Pablo
0 siblings, 0 replies; 2+ messages in thread
From: De Lara Guarch, Pablo @ 2015-02-16 10:01 UTC (permalink / raw)
To: Shankari Vaidyalingam, dev
Hi Shankari,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shankari
> Vaidyalingam
> Sent: Sunday, February 15, 2015 2:46 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Query on portmask config
>
> Hi,
>
> I'm new to DPDK.
> Would like to know how to determine the portmask for a given
> configuration.
> Does it depend on the number of cores configured
Usually portmask is parsed with the -p option (depends on the app), followed by an hexadecimal value.
So, for instance, -p 0x5 will use ports 0 and 2 from the ports bound to one of the DPDK drivers.
Regarding to your second question, number of ports are independent of number of cores.
A single core can handle several ports, and even several cores can handle a single port (using different queues).
Regards,
Pablo
>
> Regards
> Shankari.V
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-02-16 10:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-15 2:45 [dpdk-dev] Query on portmask config Shankari Vaidyalingam
2015-02-16 10:01 ` De Lara Guarch, Pablo
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).