It’s better to allow packet output from any packet type pool, no matter when the pool was created. Implementation controls packet pool memory mapping and can e.g. arrange all packet pool memory to be contiguous (in global init time). Each packet pool create could update IOMMU or if entries are scarce one or few entries could map the entire packet pool memory area.
Before – after API call relations would get cryptic and hard to maintain / debug in a complex application (multiple pktios and pools, created on different parts of the application). -Petri From: EXT Christophe Milard [mailto:[email protected]] Sent: Wednesday, December 16, 2015 5:39 PM To: Petri Savolainen; Ola Liljedahl Cc: Eric Davis; LNG ODP Mailman List Subject: Pool DMA mapping Hi, Following the discussion at the ARCH call, today, would it be reasonable to require that all packet pools that can be used by a NIC have to be created before the related nic pktio is opened? -This is implicitly required in RX, as the pool handle from which buffer should be allocated in RX is a parameter to the pktio_open() function. Is the fact that an application will not be able to transmit packets from a pool created AFTER pktio open() was called acceptable? /Christophe.
_______________________________________________ lng-odp mailing list [email protected] https://lists.linaro.org/mailman/listinfo/lng-odp
