[etherlab-users] Why does ecrt_domain_size and ecrt_domain_external_memory are reserved to kernel mode?

[hamelin.philippe at ireq.ca]

Hi,

I don't see why this implies disabling 'ecrt_domain_size' in user-space? Would you mind to merge such a patch if I submit one?

Best regards,

Philippe Hamelin

According to the mailing list (http://lists.etherlab.org/pipermail/etherlab-users/2012/001564.html), I'm not the first user requesting a user-space 'ecrt_domain_size'. 
-----Message d'origine-----
De : etherlab-users-bounces at etherlab.org [mailto:etherlab-users-bounces at etherlab.org] De la part de Florian Pose
Envoyé : 4 janvier 2013 05:23
À : etherlab-users at etherlab.org
Objet : Re: [etherlab-users] Why does ecrt_domain_size and ecrt_domain_external_memory are reserved to kernel mode?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Am 19.12.2012 15:02, schrieb hamelin.philippe at ireq.ca:
> is there a specific reason why the methods ecrt_domain_size and 
> ecrt_domain_external_memory are reserved to kernel mode? I would like 
> to copy or share the domain's data to another process using a shared 
> memory, so I have at least to know the size of the whole process data.

yes, the reason is that the process data already are in a shared memory between kernel and userspace, when using the userspace library.

- --
Viele Grüße,
Florian
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDmrXEACgkQABFOIMygR8x3YwCgipkkL6U4qyVywYbu33r77FiA
E+0AnRiVMd7MQnbRxHUxI0HYMRH4ojMn
=+lfF
-----END PGP SIGNATURE-----
_______________________________________________
etherlab-users mailing list
etherlab-users at etherlab.org
http://lists.etherlab.org/mailman/listinfo/etherlab-users