netdev - Re: [RFC/PATCH 3/3] UDP memory usage accounting (take 2): measurement

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070928143710.GA16747@2ka.mipt.ru>
Date:	Fri, 28 Sep 2007 18:37:12 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Satoshi OSHIMA <satoshi.oshima.fk@...achi.com>
Cc:	Andi Kleen <andi@...stfloor.org>, netdev <netdev@...r.kernel.org>,
	吉藤 英明 <yoshfuji@...ux-ipv6.org>,
	Yumiko SUGITA <yumiko.sugita.yf@...achi.com>,
	青木@RedHat <haoki@...hat.com>
Subject: Re: [RFC/PATCH 3/3] UDP memory usage accounting (take 2): measurement

On Fri, Sep 28, 2007 at 10:41:31PM +0900, Satoshi OSHIMA (satoshi.oshima.fk@...achi.com) wrote:
> This patch introduces memory usage measurement for UDP.
> 
> These 3 points were updated.
> 
> - UDP specific codes in IP layer were removed.
> 
> - atomic_sub() in a loop was removed
> 
> - accounting during socket destruction

Another approach is to account only at the highest UDP layer and having
datagram skb destructor just like it is done in TCP, but this approach
is also resonable.

I already told that patches 1 and 3 have broken indent, please fix that.

A hint: when you are about to submit something network related for inclusion,
and strongly believes it is ready, it can be a not that bad idea to add 
David Miller <davem@...emloft.net> to copy list, he can complain about
backlog and so on, but will read you mail twice :) but do not tell anyone.

-- 
	Evgeniy Polyakov
-
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