Home » Mailing list archives » linux-netdev » 2009 » June » 25

Socket options for different architectures (a short question)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Kevin Wilson <wkevils@...>
To: <netdev@...>
Subject: Socket options for different architectures (a short question)
Date: Thursday, June 25, 2009 - 8:42 am

Hello, netdev list,


I have a short question about socket options:

why does each architecture has a list of the socket options

it supports in a separate socket.h header ? it seems to me that the list

of these options is identical (I did not verified this though)

Is there a case when some specific platform/platforms define socket

options in a different way ?

Is there a case when some platform supports only part of the socket

options ?

For example, for


SO_DEBUG,SO_REUSEADDR, SO_SNDBUF, etc, we have the same definitions in


 arch/ia64/include/asm/socket.h, arch/xtensa/include/asm/socket.h,

 arch/x86/include/asm/socket.h ,arch/powerpc/include/asm/socket.h and so on.


Regards,

 Kevin

--

To unsubscribe from this list: send the line "unsubscribe netdev" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
Socket options for different architectures (a short question), Kevin Wilson, (Thu Jun 25, 8:42 am)