* [dpdk-users] Multiple UDP ports Per NIC
@ 2018-06-06 14:29 Kevin Kall
2018-06-07 10:10 ` Richard Nutman
0 siblings, 1 reply; 3+ messages in thread
From: Kevin Kall @ 2018-06-06 14:29 UTC (permalink / raw)
To: users
Hello,
I am brand-new to DPDK (just found out about it) and have what is likely a
simple/stupid question.
Do your libraries/framework allow for different UDP/IP packet streams being
received on a single NIC (different UDP ports) to be directed to/processed
by separate CPU cores (as if each CPU core was opening a different UDP
socket)?
Same goes for transmit - can different CPU cores transmit on separate UDP
ports on a single NIC?
If so, can someone point me to an example?
Thanks so much.
Fish
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-users] Multiple UDP ports Per NIC
2018-06-06 14:29 [dpdk-users] Multiple UDP ports Per NIC Kevin Kall
@ 2018-06-07 10:10 ` Richard Nutman
[not found] ` <CAK9TsR0GdU6eR27Pz5+nQOHhBM9ZH6GnXecuBL9QsVbXZ4rRSw@mail.gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Richard Nutman @ 2018-06-07 10:10 UTC (permalink / raw)
To: users
Hi Kevin,
This is possible if you use the rte_flow system on NIC's that support it. In older versions of DPDK it was called the Flow Director. This enables you to steer network streams to a particular receive queue, which can be processed on a particular cpu core.
See http://dpdk.org/doc/api/rte__flow_8h.html for more details;
Example; http://dpdk.org/doc/api/examples_2flow_filtering_2main_8c-example.html
Alternatively you can receive all packets on 1 or several cores (if you use something like RSS) and can sort and send to different cores if needs be.
Transmit works similar. Just set up multiple TX queues for each core you want to have active sending from.
Pay particular attention to which functions are thread-safe in DPDK, especially for packet pools.
-Richard.
> -----Original Message-----
> From: Kevin Kall [mailto:fishforish@gmail.com]
> Sent: 06 June 2018 15:30
> To: users@dpdk.org
> Subject: [dpdk-users] Multiple UDP ports Per NIC
>
> Hello,
>
> I am brand-new to DPDK (just found out about it) and have what is likely a
> simple/stupid question.
>
> Do your libraries/framework allow for different UDP/IP packet streams being
> received on a single NIC (different UDP ports) to be directed to/processed by
> separate CPU cores (as if each CPU core was opening a different UDP
> socket)?
>
> Same goes for transmit - can different CPU cores transmit on separate UDP
> ports on a single NIC?
>
> If so, can someone point me to an example?
>
> Thanks so much.
>
> Fish
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-users] [External] Re: Multiple UDP ports Per NIC
[not found] ` <CAK9TsR0GdU6eR27Pz5+nQOHhBM9ZH6GnXecuBL9QsVbXZ4rRSw@mail.gmail.com>
@ 2018-06-07 14:00 ` Richard Nutman
0 siblings, 0 replies; 3+ messages in thread
From: Richard Nutman @ 2018-06-07 14:00 UTC (permalink / raw)
To: users
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 3561 bytes --]
Hi Kevin,
You can set an interrupt to fire on receive queues when a packet arrives, but if youâre processing packets continuously you probably donât need that functionality.
I assume that is what it refers to, Iâve not worked with SolarFlare cards.
-Richard.
From: Kevin Kall [mailto:fishforish@gmail.com]
Sent: 07 June 2018 14:56
To: Richard Nutman
Cc: users@dpdk.org
Subject: [External] Re: [dpdk-users] Multiple UDP ports Per NIC
This Message originated outside your organization.
________________________________
Thank you, Richard.
Will likely be using SolarFlare NICs, and I can see that they support multiple transmit and receive queues, jumbo frames, and basic flow control, which should be what is needed.
One quick question, a SolarFlare limitation listed is lack of support for receive queue interrupts. However, the PMD documentation states "a PMD accesses the RX and TX descriptors directly without any interrupts". Thus, do you know what this limitation means?
Thanks.
-Kevin
On Thu, Jun 7, 2018 at 6:10 AM, Richard Nutman <Richard.Nutman@s-a-m.com<mailto:Richard.Nutman@s-a-m.com>> wrote:
Hi Kevin,
This is possible if you use the rte_flow system on NIC's that support it. In older versions of DPDK it was called the Flow Director. This enables you to steer network streams to a particular receive queue, which can be processed on a particular cpu core.
See http://dpdk.org/doc/api/rte__flow_8h.html for more details;
Example; http://dpdk.org/doc/api/examples_2flow_filtering_2main_8c-example.html
Alternatively you can receive all packets on 1 or several cores (if you use something like RSS) and can sort and send to different cores if needs be.
Transmit works similar. Just set up multiple TX queues for each core you want to have active sending from.
Pay particular attention to which functions are thread-safe in DPDK, especially for packet pools.
-Richard.
> -----Original Message-----
> From: Kevin Kall [mailto:fishforish@gmail.com<mailto:fishforish@gmail.com>]
> Sent: 06 June 2018 15:30
> To: users@dpdk.org<mailto:users@dpdk.org>
> Subject: [dpdk-users] Multiple UDP ports Per NIC
>
> Hello,
>
> I am brand-new to DPDK (just found out about it) and have what is likely a
> simple/stupid question.
>
> Do your libraries/framework allow for different UDP/IP packet streams being
> received on a single NIC (different UDP ports) to be directed to/processed by
> separate CPU cores (as if each CPU core was opening a different UDP
> socket)?
>
> Same goes for transmit - can different CPU cores transmit on separate UDP
> ports on a single NIC?
>
> If so, can someone point me to an example?
>
> Thanks so much.
>
> Fish
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
\x16º&\b«ØZ©ëm¹Ü¢ak§ó^8Û~¶Ó_\x11zÛ«ö\b"®'aj¶§¶çryÇ¢½ç_®®²É¥×¥÷«Ë_5)q«-r®²É¥×¥÷«Ë_5)q«-r¶×´çn5óVòvd¢¸\x0f¢Ë_\x1c"¶\x11\x1213ât\x10¶Ð\x0eõ\awè®ë\x1e®ÇivJ+Zâð§ÛM|×6ß´ÛM\x02\x11$Ã(\x12 Ú¶êÞ
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-06-07 14:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-06 14:29 [dpdk-users] Multiple UDP ports Per NIC Kevin Kall
2018-06-07 10:10 ` Richard Nutman
[not found] ` <CAK9TsR0GdU6eR27Pz5+nQOHhBM9ZH6GnXecuBL9QsVbXZ4rRSw@mail.gmail.com>
2018-06-07 14:00 ` [dpdk-users] [External] " Richard Nutman
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).