Re: Why use volatile for socket state?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

Why do we need the socket state (for the nework layer
representation of the sockets) to be
 volatile?
It is implemented as volatile unsigned  char skc_state in
struct sock_common .

I personally think this is done to prevent looking up the state on the
CPU registers. In other word, query is always directed toward physical
memory. Yes, it lowers the perfomance but maybe it is designed that
way so we won't get wrong socket state.

regards,

Mulyadi
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux