Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Sep 2018 14:41:31 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 231151] ifconfig: unable to disable rxcsum, rxcsum6 and vlanhwcsum on em driver
Message-ID:  <bug-231151-7501-4ptVMm7niq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-231151-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-231151-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231151

--- Comment #6 from Stephen Hurd <shurd@FreeBSD.org> ---
(In reply to Kaho Toshikazu from comment #3)

> I think iflib should not do a special thing, and it is better that
> an individual driver has some workarounds if need.

The driver isn't involved in this ioctl, so it needs to support the lowest
common denominator of iflib devices.  This ioctl works by stopping the driv=
er,
setting the capabilities, then restarting the driver... which then applies =
the
capabilities.

If a driver can't support a particular combination of flags, there's no way=
 for
it to tell iflib at this time.  For rxcsum, the ifconfig specifically menti=
ons
that rxcsum and rxcsum6 may not be interdependent.

It looks like there's some brokenness in the WoL stuff too.  I'm digging in=
to
that once I verify your vlan_hwcsum changes.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231151-7501-4ptVMm7niq>