netdev - Re: [PATCH net-next] net/mlx4: use one page fragment per incoming frame

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]

Date:	Mon, 03 Jun 2013 11:12:30 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Rick Jones <rick.jones2@...com>
Cc:	David Miller <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>, Amir Vadai <amirv@...lanox.com>
Subject: Re: [PATCH net-next] net/mlx4: use one page fragment per incoming
 frame

On Mon, 2013-06-03 at 11:05 -0700, Rick Jones wrote:

> I take it this is a > 10 Gbit/s NIC?
> 

Well, I guess so !

Or something is really strange with this NIC !

> What if any is the downside to an incoming stream of small packets?

These kind of NIC are aimed for performance, I was told.

1) It would be strange to use them on memory constrained machines.

2) using 1536 bytes fragments is better than most other NIC drivers, as
they usually use 2048 or 4096 bytes frags

3) Current memory allocations done in mlx4 uses order-2 pages, and
nobody yet complained that these allocation might fail...



--
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