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
| ||
|
Date: Fri, 21 Dec 2007 19:22:11 -0500 From: Hideo AOKI <haoki@...hat.com> To: David Miller <davem@...emloft.net> CC: herbert@...dor.apana.org.au, netdev@...r.kernel.org, tyasui@...hat.com, mhiramat@...hat.com, satoshi.oshima.fk@...achi.com, billfink@...dspring.com, andi@...stfloor.org, johnpol@....mipt.ru, shemminger@...ux-foundation.org, yoshfuji@...ux-ipv6.org, yumiko.sugita.yf@...achi.com Subject: Re: [PATCH 2/4] [CORE]: datagram: basic memory accounting functions David Miller wrote: > From: Hideo AOKI <haoki@...hat.com> > Date: Thu, 20 Dec 2007 23:18:54 -0500 > >>> Also, the memory accounting is done at different parts in >>> the socket code paths for stream vs. datagram. This is why >>> everything is inconsistent, and, a mess. >> Could you tell me more detailed information? > > I think the core thing is that TCP and INET protocols call into > the memory accounting internally, either inside their own code > paths or with inet_*() helpers. > > This is versus what we really want is everything happening via generic > sk_foo() helpers. > > If that's what's happening already, great, just consolidate the > datagram vs. stream stuff and it should be good. Thank you for the explanation. I'll do my best. Regards, Hideo -- Hitachi Computer Products (America) Inc. -- 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