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, 06 Feb 2009 01:17:22 -0800 (PST) From: David Miller <davem@...emloft.net> To: jarkao2@...il.com Cc: herbert@...dor.apana.org.au, zbr@...emap.net, w@....eu, dada1@...mosbay.com, ben@...s.com, mingo@...e.hu, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, jens.axboe@...cle.com Subject: Re: [PATCH v2] tcp: splice as many packets as possible at once From: Jarek Poplawski <jarkao2@...il.com> Date: Fri, 6 Feb 2009 09:10:34 +0000 > Hmm... I don't get it. It seems these slabs do a lot of advanced work, > and still some people like Evgeniy or Nick thought it's not enough, > and even found it worth of their time to rework this. Note that, at least to some extent, the memory allocators are duplicating some of the locality and NUMA logic that's already present in the page allocator itself. Except that they are handling the fact that objects are moving around instead of pages. Also keep in mind that we might also want to encourage drivers to make use of the SKB recycling mechanisms we have. So this will decrease lifetimes, and thus the wastage and locality issues immensely. We truly want something different from what the general purpose allocator provides. Namely, a reference countable buffer. And all I'm saying is that since the page allocator provides that facility, and using pages solves all of the splice() et al. problems, building something extremely simple on top of the page allocator seems to be a good way to go. -- 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