On Mon, Jun 05, 2017 at 16:13 +0200, Mike Belopuhov wrote:
> On Wed, May 31, 2017 at 20:40 +0200, Mike Belopuhov wrote:
> > According to the FreeBSD driver, txp(4) is not setting up its TX
> > ring correctly. FreeBSD driver uses up to 16 fragments, while we
> > use up to 252 which is suspicious.
On Wed, May 31, 2017 at 20:40 +0200, Mike Belopuhov wrote:
> According to the FreeBSD driver, txp(4) is not setting up its TX
> ring correctly. FreeBSD driver uses up to 16 fragments, while we
> use up to 252 which is suspicious.
>
> This gets us in line with FreeBSD, introduces goodness of
On Wed, May 31, 2017 at 20:40 +0200, Mike Belopuhov wrote:
> According to the FreeBSD driver, txp(4) is not setting up its TX
> ring correctly. FreeBSD driver uses up to 16 fragments, while we
> use up to 252 which is suspicious.
>
> This gets us in line with FreeBSD, introduces goodness of
According to the FreeBSD driver, txp(4) is not setting up its TX
ring correctly. FreeBSD driver uses up to 16 fragments, while we
use up to 252 which is suspicious.
This gets us in line with FreeBSD, introduces goodness of m_defrag
and removes pesky if_deq_* thingies.
Does anyone still have the