netdev - Re: [PATCH 4/5] unix_diag: Report memory usage info

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20111228.140052.1612142433959503905.davem@davemloft.net>
Date:	Wed, 28 Dec 2011 14:00:52 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	xemul@...allels.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 4/5] unix_diag: Report memory usage info

From: Pavel Emelyanov <xemul@...allels.com>
Date: Wed, 28 Dec 2011 22:55:59 +0400

> On 12/28/2011 05:39 PM, Pavel Emelyanov wrote:
>> Symmetrical to inet sockets, but unix only have two meaningful
>> values -- the wmem allocation and sndbuf.
>> 
>> Signed-off-by: Pavel Emelyanov <xemul@...allels.com>
> 
> David, taking into account you don't apply patch #3, please, ignore this and the 5th
> ones

I always toss the entire set of patches when any of the individual
ones need changes.

> (but your feedback about whether reporting the ack backlog info in the same place
> whith the meminfo is still required)

I don't understand what you need to know from me.

The sk_max_ack_backlog needs to stay where it is right now, and I would advise
that you present it in the same way TCP does for other protocols.

What else do you need to know?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html