Go to file
John Daley f201fd0585 net/enic: fix max packet length check
When the device was configured with an explicit maximum packet length,
it would fail if the value was greater than MTU configured in CIMC/UCSM
(plus L2 header length). It should have been compared against maximum
allowed by the device.

Fixes: bb34ffb848 ("net/enic: determine max egress packet size and max MTU")

Signed-off-by: John Daley <johndale@cisco.com>
2016-11-07 18:01:11 +01:00
app app/testpmd: fix DCB configuration 2016-11-07 16:55:59 +01:00
buildtools pmdinfogen: fix clang build 2016-10-04 11:50:56 +02:00
config crypto/openssl: rename libcrypto to openssl 2016-10-26 14:58:37 +02:00
doc net/i40e: fix floating VEB 2016-11-07 17:43:09 +01:00
drivers net/enic: fix max packet length check 2016-11-07 18:01:11 +01:00
examples vhost: remove references to vhost-cuse 2016-11-07 15:59:21 +01:00
lib vhost: remove references to vhost-cuse 2016-11-07 15:59:21 +01:00
mk ethdev: rename library for consistency 2016-11-06 20:53:23 +01:00
pkg version: 16.07.0 2016-07-28 20:48:41 +02:00
scripts scripts: remove zlib dependency to test qede build 2016-11-06 20:53:19 +01:00
tools tools: bind crypto devices 2016-10-04 20:41:09 +02:00
.gitignore doc: generate NIC overview table from ini files 2016-08-03 18:42:17 +02:00
GNUmakefile pmdinfogen: add buildtools and pmdinfogen utility 2016-07-06 22:34:39 +02:00
LICENSE.GPL doc: GPL/LGPL licenses 2013-07-25 14:43:06 +02:00
LICENSE.LGPL doc: fix file format (dos to unix) 2013-09-06 11:43:07 +02:00
MAINTAINERS scripts: show fixes with release version of bug 2016-11-05 15:47:36 +01:00
Makefile remove trailing whitespaces 2014-06-11 00:29:34 +02:00
README doc: add readme file 2015-12-13 22:06:58 +01:00

DPDK is a set of libraries and drivers for fast packet processing.
It supports many processor architectures and both FreeBSD and Linux.

The DPDK uses the Open Source BSD license for the core libraries and
drivers. The kernel components are GPLv2 licensed.

Please check the doc directory for release notes,
API documentation, and sample application information.

For questions and usage discussions, subscribe to: users@dpdk.org
Report bugs and issues to the development mailing list: dev@dpdk.org