Darren Reed wrote:
Yunsong (Roamer) Lu wrote:
...
The simplest way to fix the CR is let snoop to check the LSO
information with the packet and avoid warning it. But I'm not sure
it's enough.
Is that enough?
Even though the system shouldn't do it, if an mblk_t is marked with LSO
information and delivered to a driver that doesn't support it, it will
then attempt to transmit the packet as-is, correct?
I don't think snoop is supposed to do all sanity check for the driver.
Actually it's simple for the snoop users to figure out such misbehavior
without seeing a warning.
If snoop should warn the user for such misbehaviors, it will have to
check all NIC's capabilities, like hcksum, but not only LSO. This seems
"nice" but unnecessary.
Thanks,
Roamer
--
# telnet (650)-786-6759 (x86759)
Connected to Solaris.Sun.COM.
login: Lu, Yunsong
Last login: January 2, 2007 from beyond.sfbay
[email protected] v1.04 Since Mon Dec. 22, 2003
[roa...@solaris Networking]# cd ..
_______________________________________________
networking-discuss mailing list
[email protected]
