lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100622143102.68a59849@dhcp-lab-109.englab.brq.redhat.com>
Date:	Tue, 22 Jun 2010 14:31:02 +0200
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	Amerigo Wang <amwang@...hat.com>, netdev@...r.kernel.org,
	nhorman@...hat.com, herbert.xu@...hat.com,
	Ramkrishna.Vepa@...r.com, davem@...emloft.net
Subject: Re: [v4 Patch 1/2] s2io: add dynamic LRO disable support

On Tue, 22 Jun 2010 12:44:40 +0100
Ben Hutchings <bhutchings@...arflare.com> wrote:

> On Tue, 2010-06-22 at 04:50 -0400, Amerigo Wang wrote:
> > This patch adds dynamic LRO diable support for s2io net driver.
> > 
> > (I don't have s2io card, so only did compiling test. Anyone who wants
> > to test this is more than welcome.)
> > 
> > This is based on Neil's initial work, and heavily modified
> > based on Ramkrishna's suggestions.
> [...]
> > +static int s2io_ethtool_set_flags(struct net_device *dev, u32 data)
> > +{
> > +	struct s2io_nic *sp = netdev_priv(dev);
> > +	int rc = 0;
> > +	int changed = 0;
> > +
> > +	if (data & ~ETH_FLAG_LRO)
> > +		return -EOPNOTSUPP;
> > +
> > +	if (data & ETH_FLAG_LRO) {
> > +		if (lro_enable) {
> > +			if (!(dev->features & NETIF_F_LRO)) {
> > +				dev->features |= NETIF_F_LRO;
> > +				changed = 1;
> > +			}
> > +		} else
> > +			rc = -EOPNOTSUPP;
> 
> Should lro_enable=0 really prevent enabling it later?  This seems
> unusual.

We are doing this in bnx2x. Current Amerigo patch change to the
same behavior mlx4. For me that have sense - if you want to disallow
LRO - use module option.

In this case however lro_enable variable looks obsolete from times
where there was no ethtool possibility to dynamic set/unset LRO.
Perhaps it should be removed at all, but maybe not as part
of that patch.

Stanislaw
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ