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 > 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] > 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 --------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com --------------------------------------------------------------------------------------- º&‚«‰ØZ­©ëm¹Ü¢akˆ›§ó^8Û~¶Ó_zÛ«œö­†"®'aj¶§­¶çr‰‘yÇ¢½ç_®‰®²É­¥×¥Š÷«Ë_5š)žq«-r‰®²É­¥×¥Š÷«Ë_5š)žq«-r‰¶×­´çn5óVòv—d¢¸¢Ë_‹"¶13ât¶Ðõwè®ë®ÇivJ+€Zâð›§ÛM|׎6ߟ´ÛM$Ã(ƒŠ Ú¶êÞ