From: David Miller <davem@davemloft.net>
To: johunt@akamai.com
Cc: netdev@vger.kernel.org, edumazet@google.com, jbaron@akamai.com,
ckuiper@google.com, pgynther@google.com
Subject: Re: [PATCH] sock: introduce SO_MEMINFO getsockopt
Date: Wed, 22 Mar 2017 11:20:24 -0700 (PDT) [thread overview]
Message-ID: <20170322.112024.157764600434310885.davem@davemloft.net> (raw)
In-Reply-To: <1490037723-6475-1-git-send-email-johunt@akamai.com>
From: Josh Hunt <johunt@akamai.com>
Date: Mon, 20 Mar 2017 15:22:03 -0400
> Allows reading of SK_MEMINFO_VARS via socket option. This way an
> application can get all meminfo related information in single socket
> option call instead of multiple calls.
>
> Adds helper function, sk_get_meminfo(), and uses that for both
> getsockopt and sock_diag_put_meminfo().
>
> Suggested by Eric Dumazet.
>
> Signed-off-by: Josh Hunt <johunt@akamai.com>
> Reviewed-by: Jason Baron <jbaron@akamai.com>
> Acked-by: Eric Dumazet <edumazet@google.com>
Applied, thanks.
prev parent reply other threads:[~2017-03-22 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 19:22 [PATCH] sock: introduce SO_MEMINFO getsockopt Josh Hunt
2017-03-22 18:20 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170322.112024.157764600434310885.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ckuiper@google.com \
--cc=edumazet@google.com \
--cc=jbaron@akamai.com \
--cc=johunt@akamai.com \
--cc=netdev@vger.kernel.org \
--cc=pgynther@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).