Hi,
HelenOS does not use Berkeley Sockets API as the network transport layer
interface. We use our own API that does not use numerical descriptors as
handles. See uspace/lib/c/include/inet/[tcp|udp].h. A TCP connection is
identified via tcp_conn_t *, a listener by tcp_listener_t *, UDP association
by udp_assoc_t *, etc.
There is currently no way to access a network connection via the file API.
It would be possible to implement, but there has been no motivation to do so
as of yet.
Also note that the fact a VFS client identifies open files via an 'int' as
UNIX does should be considered incidental and may change in the future.
Best regards,
Jiri
---------- Původní e-mail ----------
Od: wangjianjian (C) <[email protected]>
Komu: HelenOS development mailing list <[email protected]>
Datum: 28. 2. 2019 9:17:18
Předmět: [HelenOS-devel] 答复: HelenOS socket(fd) management
"Seems that in Micro-kernel, fd/socket are in different name space natively
because they go to different servers.
But sometimes, a fd/socket may be valid for both FS and network. How do we
differ them?
Any comments about this?
-----邮件原件-----
发件人: wangjianjian (C)
发送时间: 2019年2月28日 15:58
收件人: [email protected]
主题: HelenOS socket(fd) management
Hi all,
In HelenOS, FS's fd is managed by VFS, from a fixed-size array. But for
network, how socket, which we can see it as another kind of fd, comes from?
For a single process, are they managed separately? I don't find socket from
code.
I glance at Minix3 's code, seems they manage FS fd and socket separately,
which means they can be same for a process.
Thanks for your help.
Best,
Jakub
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
"
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
