netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Cliburn <jacliburn@bellsouth.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: jeff@garzik.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, link@miggy.org, ian@jeffray.co.uk,
	csnook@redhat.com, jie.yang@atheros.com, m@fhloston.org,
	davem@davemloft.net
Subject: Re: [PATCH] atl1: disable TSO by default
Date: Tue, 19 Aug 2008 17:53:34 -0500	[thread overview]
Message-ID: <20080819175334.28dc1c8e@osprey.hogchain.net> (raw)
In-Reply-To: <E1KVQyr-0001Ui-00@gondolin.me.apana.org.au>

On Tue, 19 Aug 2008 23:10:37 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:

> Jay Cliburn <jacliburn@bellsouth.net> wrote:

> >        netdev->features |= NETIF_F_LLTX;
> 
> Another new driver using LLTX, this is not good when we're trying
> to get rid of it.

The atl1 driver was merged in the spring of 2007, so I'm not sure I
consider it new (but your kernel development time horizon is undoubtedly
*way* longer than mine, so you may indeed consider it new). It was
basically a vendor driver that we modified to conform to kernel coding
standards. It started life, we believe, as pretty much a clone of the
e1000 driver circa 2005, so that's likely where it's use of LLTX
came from.

> 
> Perhaps we could just kill it by ignoring the LLTX flag and always
> grabbing the xmit lock.  That should be safe as long as none of these
> drivers grab the xmit lock within their private locks.

I'd be happy to gin up a patch if you could point me to a driver that
implements properly what you're asking.

Thanks,
Jay

  reply	other threads:[~2008-08-19 22:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19  0:28 [PATCH] atl1: disable TSO by default Jay Cliburn
2008-08-19 13:10 ` Herbert Xu
2008-08-19 22:53   ` Jay Cliburn [this message]
2008-08-19 22:58     ` David Miller
2008-08-19 23:17       ` Herbert Xu
2008-08-27  9:37 ` Jeff Garzik

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=20080819175334.28dc1c8e@osprey.hogchain.net \
    --to=jacliburn@bellsouth.net \
    --cc=csnook@redhat.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=ian@jeffray.co.uk \
    --cc=jeff@garzik.org \
    --cc=jie.yang@atheros.com \
    --cc=link@miggy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m@fhloston.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).