Searched hist:f02db315 (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/net/ipv4/ |
H A D | ip_sockglue.c | f02db315 Tue Sep 24 08:43:08 CDT 2013 Francesco Fusco <ffusco@redhat.com> ipv4: IP_TOS and IP_TTL can be specified as ancillary data
This patch enables the IP_TTL and IP_TOS values passed from userspace to be stored in the ipcm_cookie struct. Three fields are added to the struct:
- the TTL, expressed as __u8. The allowed values are in the [1-255]. A value of 0 means that the TTL is not specified.
- the TOS, expressed as __s16. The allowed values are in the range [0,255]. A value of -1 means that the TOS is not specified.
- the priority, expressed as a char and computed when handling the ancillary data.
Signed-off-by: Francesco Fusco <ffusco@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net> f02db315 Tue Sep 24 08:43:08 CDT 2013 Francesco Fusco <ffusco@redhat.com> ipv4: IP_TOS and IP_TTL can be specified as ancillary data This patch enables the IP_TTL and IP_TOS values passed from userspace to be stored in the ipcm_cookie struct. Three fields are added to the struct: - the TTL, expressed as __u8. The allowed values are in the [1-255]. A value of 0 means that the TTL is not specified. - the TOS, expressed as __s16. The allowed values are in the range [0,255]. A value of -1 means that the TOS is not specified. - the priority, expressed as a char and computed when handling the ancillary data. Signed-off-by: Francesco Fusco <ffusco@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/include/net/ |
H A D | ip.h | f02db315 Tue Sep 24 08:43:08 CDT 2013 Francesco Fusco <ffusco@redhat.com> ipv4: IP_TOS and IP_TTL can be specified as ancillary data
This patch enables the IP_TTL and IP_TOS values passed from userspace to be stored in the ipcm_cookie struct. Three fields are added to the struct:
- the TTL, expressed as __u8. The allowed values are in the [1-255]. A value of 0 means that the TTL is not specified.
- the TOS, expressed as __s16. The allowed values are in the range [0,255]. A value of -1 means that the TOS is not specified.
- the priority, expressed as a char and computed when handling the ancillary data.
Signed-off-by: Francesco Fusco <ffusco@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net> f02db315 Tue Sep 24 08:43:08 CDT 2013 Francesco Fusco <ffusco@redhat.com> ipv4: IP_TOS and IP_TTL can be specified as ancillary data This patch enables the IP_TTL and IP_TOS values passed from userspace to be stored in the ipcm_cookie struct. Three fields are added to the struct: - the TTL, expressed as __u8. The allowed values are in the [1-255]. A value of 0 means that the TTL is not specified. - the TOS, expressed as __s16. The allowed values are in the range [0,255]. A value of -1 means that the TOS is not specified. - the priority, expressed as a char and computed when handling the ancillary data. Signed-off-by: Francesco Fusco <ffusco@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|