From: Jeff Garzik <jeff@garzik.org>
To: Chris Snook <csnook@redhat.com>
Cc: Kevin Hao <kexin.hao@windriver.com>,
Jeff Garzik <jgarzik@redhat.com>,
Jay Cliburn <jacliburn@bellsouth.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: remove LLTX in atl2 driver
Date: Thu, 25 Sep 2008 16:55:17 -0400 [thread overview]
Message-ID: <48DBFAB5.2010709@garzik.org> (raw)
In-Reply-To: <48DBF4DD.8060908@redhat.com>
Chris Snook wrote:
> Kevin Hao wrote:
>> When NETIF_F_LLTX is set, the atlx driver will use a private lock.
>> But in recent kernels this implementation seems redundant and
>> can cause problems where AF_PACKET sees things twice. Since
>> NETIF_F_LLTX is marked as deprecated and shouldn't be used in
>> new driver, this patch removes NETIF_F_LLTX and adds a mmiowb
>> before sending packet.
>>
>> Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
>
> Can you explain a bit more concretely the problem this solves, and your
> testing? Ultimately we'll want to merge this code with the atl1 code,
> so we need to be confident that we can and should make the same change
> there.
>
> -- Chris
>
>> ---
>> drivers/net/atlx/atl2.c | 24 +-----------------------
>> drivers/net/atlx/atl2.h | 1 -
>> 2 files changed, 1 insertions(+), 24 deletions(-)
Not directly addressing your question, but LLTX is indeed deprecated and
in general we want to move away from it.
Jeff
next prev parent reply other threads:[~2008-09-25 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 0:35 [PATCH] net: remove LLTX in atl2 driver Kevin Hao
2008-09-25 20:30 ` Chris Snook
2008-09-25 20:55 ` Jeff Garzik [this message]
2008-09-25 22:34 ` Chris Snook
2008-09-25 23:58 ` Jay Cliburn
2008-09-26 1:20 ` Kevin Hao
2008-09-26 1:24 ` Chris Snook
2008-09-26 2:20 ` Kevin Hao
2008-09-26 1:24 ` Jay Cliburn
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=48DBFAB5.2010709@garzik.org \
--to=jeff@garzik.org \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=jgarzik@redhat.com \
--cc=kexin.hao@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).