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: Sat, 5 Aug 2006 20:33:07 +1000 From: Herbert Xu <herbert@...dor.apana.org.au> To: Evgeniy Polyakov <johnpol@....mipt.ru> Cc: Jesse Brandeburg <jesse.brandeburg@...il.com>, Chris Leech <chris.leech@...il.com>, arnd@...dnet.de, olel@....pl, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: problems with e1000 and jumboframes On Sat, Aug 05, 2006 at 02:24:36PM +0400, Evgeniy Polyakov wrote: > > > If we had a flag to indicate writability we could also have a flag to > > indicate that the memory comes from kmalloc rather than alloc_page. > > Yes, that would be good, but who will give us a bit in the struct page? > Can we recreate frag_list elements to be a bitmasks and steal couple > of them there, so we would not increase fragment's structure size? I wasn't thinking of a bit in struct page, but rather a bit in skb_frag_t. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists