Add support for build option for Nameservice

[galak]

Name service functionality isn't always needed, add a build option to reduce the footprint.

[jorisvanderpol]

Hi,

I considered the name service as a way that the communication is up between master and slave (although I saw a blocking call at the slave side in the virtqueue component). If you have a single channel, between for example one APU process (master) and one RPU process (slave), you do know when the other side is ready to receive messages? And is there a proper way disable the name service functionality now?

Kind regards,

Joris

[arnopo]

Hi @jorisvanderpol

Hi,

I considered the name service as a way that the communication is up between master and slave (although I saw a blocking call at the slave side in the virtqueue component). If you have a single channel, between for example one APU process (master) and one RPU process (slave), you do know when the other side is ready to receive messages?

Today the side that receives the NS announcement has to send the first message. if the NS is not used and addresses are fixed, the same restriction exist.
This is something that as been identified as an improvement to add to the RPMsg protocol.

And is there a proper way disable the name service functionality now?

By disabling the VIRTIO_RPMSG_F_NS virtio feature in the resource table

Kind regards,

Joris