linux-kernel - Re: problems with e1000 and jumboframes

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: <E1G8sif-0003oY-00@gondolin.me.apana.org.au>
Date:	Fri, 04 Aug 2006 15:59:37 +1000
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	chris.leech@...il.com (Chris Leech)
Cc:	arnd@...dnet.de, johnpol@....mipt.ru, olel@....pl,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: problems with e1000 and jumboframes

Chris Leech <chris.leech@...il.com> wrote:
> 
> We could try and only use page allocations for older e1000 devices,
> putting headers and payload into skb->frags and copying the headers
> out into the skb->data area as needed for processing.  That would do
> away with large allocations, but in Jesse's experiments calling
> alloc_page() is slower than kmalloc(), so there can actually be a
> performance hit from trying to use page allocations all the time.

Interesting.  Could you guys post figures on alloc_page speed vs. kmalloc?

Also, getting memory slower is better than not getting them at all :)
-- 
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/