On 01/22/2014 04:11 PM, Dan Ballard wrote:
Provides a new option for setsockopt SO_MAX_DGRAM_QLEN that sets and
gets a socket specific max datagram queue length. Currently each socket
has one but it's only ever initialized from
/proc/sys/net/unix/max_dgram_qlen and then never adjustable later. Now
each socket can have it individually tweaked during it's life.

Signed-off-by: Dan Ballard <[email protected]>
---
  include/uapi/asm-generic/socket.h |    2 ++
  net/core/sock.c                   |    7 +++++++
  2 files changed, 9 insertions(+)

diff --git a/include/uapi/asm-generic/socket.h 
b/include/uapi/asm-generic/socket.h
index 38f14d0..f8c3e6b 100644
--- a/include/uapi/asm-generic/socket.h
+++ b/include/uapi/asm-generic/socket.h
@@ -80,4 +80,6 @@

  #define SO_MAX_PACING_RATE     47

+#define SO_MAX_DGRAM_QLEN      48
+

This needs to be added in more than just asm-generic, e.g.
have a look at SO_MAX_PACING_RATE or SO_BPF_EXTENSIONS.

Also you might need to rebase to current net-next head and
maybe describe use cases more in-depth; next to what Hannes
just commented.

  #endif /* __ASM_GENERIC_SOCKET_H */
diff --git a/net/core/sock.c b/net/core/sock.c
index 5393b4b..1ff69d1 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -915,6 +915,10 @@ set_rcvbuf:
                                          sk->sk_max_pacing_rate);
                 break;

+       case SO_MAX_DGRAM_QLEN:
+               sk->sk_max_ack_backlog = val;
+               break;
+
         default:
                 ret = -ENOPROTOOPT;
                 break;
@@ -1182,6 +1186,9 @@ int sock_getsockopt(struct socket *sock, int level, int 
optname,
                 v.val = sk->sk_max_pacing_rate;
                 break;

+       case SO_MAX_DGRAM_QLEN:
+               v.val = sk->sk_max_ack_backlog;
+               break;
         default:
                 return -ENOPROTOOPT;
         }
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to