Anthony Liguori <[EMAIL PROTECTED]> wrote on 17.05.2007 16:22:23:
> Is there anything that explains what the fields in sockaddr mean:
>
> sa_family_t siucv_family;
> unsigned short siucv_port; /* Reserved */
> unsigned int siucv_addr; /* Reserved */
> char siucv_nodeid[8]; /* Reserved */
> char siucv_user_id[8]; /* Guest User Id */
> char siucv_name[8]; /* Application Name */
There is a small description in "Device Drivers, Features, and
Commands SC33-8289-03" on page 211 (its page 235 if you use the pdf
viewer page number)
http://download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l26cdd03.pdf
(the file is 6.7 MB)
More generic information about iucv can be found in in
http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/zvmpdf/zvm52.html
or to be precise:
http://publibz.boulder.ibm.com/epubs/pdf/hcse5b11.pdf part 2. (11 MB)
That said, AF_IUCV builds on top of iucv and therefore requires z/VM
as hypervisor. I dont think that KVM should implement (af_)iucv. But
(af_)iucv shows several aspects how to make things good and bad.
(e.g. AF_IUCV as procotol on top of iucv was first defined in
CMS several years ago and is, therefore, not very smp-friendly.
On the other hand iucv itself offers modern features like
scatter/gather).
Back to the old question:
If shared memory or socket is better - I dont know. z/VM has both, see
dcss for its shared memory support.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
