From: David Miller <davem@davemloft.net>
To: amwang@redhat.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sgruszka@redhat.com,
herbert.xu@redhat.com, bhutchings@solarflare.com,
Ramkrishna.Vepa@exar.com
Subject: Re: [v4 Patch 2/2] mlx4: add dynamic LRO disable support
Date: Mon, 28 Jun 2010 23:04:59 -0700 (PDT) [thread overview]
Message-ID: <20100628.230459.232745316.davem@davemloft.net> (raw)
In-Reply-To: <20100622085426.5566.51436.sendpatchset@localhost.localdomain>
From: Amerigo Wang <amwang@redhat.com>
Date: Tue, 22 Jun 2010 04:50:17 -0400
>
> This patch adds dynamic LRO diable support for mlx4 net driver.
> It also fixes a bug of mlx4, which checks NETIF_F_LRO flag in rx
> path without rtnl lock.
>
> (I don't have mlx4 card, so only did compiling test. Anyone who wants
> to test this is more than welcome.)
>
> This is based on Neil's initial work too, and heavily modified based
> on Stanislaw's suggestions.
>
> Signed-off-by: WANG Cong <amwang@redhat.com>
> Signed-off-by: Neil Horman <nhorman@redhat.com>
> Acked-by: Neil Horman <nhorman@redhat.com>
> Reviewed-by: Stanislaw Gruszka <sgruszka@redhat.com>
> Cc: Ben Hutchings <bhutchings@solarflare.com>
Applied to net-next-2.6
I'd really like the module options to just die as the dynamic
ethtool mechanism should be the only knob for this for consistency
with the rest of the drivers.
next prev parent reply other threads:[~2010-06-29 6:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 8:50 [v4 Patch 1/2] s2io: add dynamic LRO disable support Amerigo Wang
2010-06-22 8:50 ` [v4 Patch 2/2] mlx4: " Amerigo Wang
2010-06-29 6:04 ` David Miller [this message]
2010-06-22 11:44 ` [v4 Patch 1/2] s2io: " Ben Hutchings
2010-06-22 12:31 ` Stanislaw Gruszka
2010-06-25 8:59 ` Cong Wang
2010-06-25 4:33 ` Jon Mason
2010-06-25 9:01 ` Cong Wang
2010-06-25 4:45 ` [PATCH] " Jon Mason
2010-06-25 9:09 ` Cong Wang
2010-06-29 6:04 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100628.230459.232745316.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ramkrishna.Vepa@exar.com \
--cc=amwang@redhat.com \
--cc=bhutchings@solarflare.com \
--cc=herbert.xu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sgruszka@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).