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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 01 Oct 2007 22:52:27 +0900 From: Satoshi OSHIMA <satoshi.oshima.fk@...achi.com> To: Evgeniy Polyakov <johnpol@....mipt.ru> Cc: Andi Kleen <andi@...stfloor.org>, netdev <netdev@...r.kernel.org>, ?? ?? <yoshfuji@...ux-ipv6.org>, Yumiko SUGITA <yumiko.sugita.yf@...achi.com>, "??@...Hat" <haoki@...hat.com>, David Miller <davem@...emloft.net>, Herbert Xu <herbert@...dor.apana.org.au> Subject: Re: [RFC/PATCH 3/3] UDP memory usage accounting (take 2): measurement Evgeniy Polyakov wrote: > 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. This patch set try to introduce a memory accounting by the page because TCP does. And ip_append_data() merges payloads to a sk_buff if previous sk_buff has enough space. The problem is that udp_append_data() doesn't recognize whether this merge happens or not. If the accounting must be in UDP layer, we need to change the interface of ip_append_data() to know this merge happens. Once the interface is changed, we have to maintain other protocol stacks to keep up with the change. But I didn't want to do it to keep this patch set small in the first step. > I already told that patches 1 and 3 have broken indent, please fix that. Oops! I will 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. Thank you for your advice. I will do that! Satoshi Oshima - 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
Powered by blists - more mailing lists