On 10/21/2014 06:52 PM, Gilad Ben Yossef wrote:
Quick question –
What are the assumptions about an odp_buffer_t ?
For example -
Can an application assume the odp_buffer_t is always the same for the
same buffer? I would assume no.
For current linux-generic implementation it's so. For other I think it's
the same. odp_buffer_t is offset in pool, which always points to the
same memory.
Can an application assume the odp_buffer_t is globally unique? I would
assume no.
yes, why no? again in linux-generic odp_buffer_t is coded by bits
<pool_id, index offset>, so it's point to exact memory address. Soc use
the same thing I think.
Can an application assume the odp_buffer_t it may be passed via shared
memory and be expected keep its meaning? I would assume no.
That depends. If it's transfered in the same process then it will be
same odp_buffer_t. If it's separate process and shared memory between
them then to have the same odp_buffer_t you need to have the same table
for pool entries. I.e. if you do fork() after odp_global_init() it will
be the same. If it's completely 2 separate process and shared memory
between them, than ... it's possible to do that, but definitely not
implemented now.
Maxim.
Anyone has any thought about this?
Thanks,
Gilad
*Gilad Ben-Yossef*
Software Architect
EZchip Technologies Ltd.
37 Israel Pollak Ave, Kiryat Gat 82025 ,Israel
Tel: +972-4-959-6666 ext. 576, Fax: +972-8-681-1483
Mobile: +972-52-826-0388, US Mobile: +1-973-826-0388
Email: [email protected] <mailto:[email protected]>, Web:
http://www.ezchip.com <http://www.ezchip.com/>
//
/"Ethernet always wins."/
— Andy Bechtolsheim//
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp
