Stephen Hemminger wrote:

On Mon, 10 Mar 2008 18:07:07 +0000
Ben Hutchings [off-list ref] wrote:

quoted

Stephen Hemminger wrote:

<snip>

quoted

quoted

@@ -1559,12 +1566,20 @@ static int do_goffload(int fd, struct ifreq *ifr)
 		allfail = 0;
 	}
 
+	eval.cmd = ETHTOOL_GFLAGS;
+	ifr->ifr_data = (caddr_t)&eval;
+	err = ioctl(fd, SIOCETHTOOL, ifr);
+	if (!err) {
+		lro = eval.data & ETH_FLAG_LRO;
+		allfail = 0;
+	}
+

To be consistent, this should print a specific error if the ioctl
fails.

No, since most hardware won't support LRO or the flags, it makes sense not
to complain when fetching the value.

<snip>

Many of the other offloads have the same issue, particularly when
using a new ethtool with an old kernel.  Maybe we should not print an
error message if the error is EOPNOTSUPP or EPERM (unknown commands
are assumed to require admin capability).  But that's a separate
change and again it's not specific to LRO.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.