netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, bhutchings@solarflare.com,
	buytenh@wantstofly.org, netdev@vger.kernel.org,
	akarkare@marvell.com, nico@cam.org, dale@farnsworth.org
Subject: Re: using software TSO on non-TSO capable netdevices
Date: Thu, 07 Aug 2008 13:32:05 -0700	[thread overview]
Message-ID: <489B5BC5.3030600@hp.com> (raw)
In-Reply-To: <20080806.230741.137564172.davem@davemloft.net>

David Miller wrote:
> So I had this idea.  My goal is to minimize the number of DMA
> mappings the driver has to make.
> 
> We don't touch anything in the original TSO skb.  However we expand
> the headroom (if necessary) and in the area in front of skb->data we
> build the header areas for the sub-TSO frames, one by one.
> 
> We give the driver some iterator functions that walk through the
> header areas and compute offset/length pairs into the
> skb_shared_info() page list.

Is that like Solaris Multi Data Transmit?

rick jones

  parent reply	other threads:[~2008-08-07 20:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 23:50 using software TSO on non-TSO capable netdevices Lennert Buytenhek
2008-07-30 23:56 ` David Miller
2008-07-31  0:41   ` Lennert Buytenhek
2008-07-31  1:10     ` David Miller
2008-07-31  1:45       ` Lennert Buytenhek
2008-07-31  3:54         ` Herbert Xu
2008-07-31  9:45           ` Lennert Buytenhek
2008-07-31 10:55             ` Herbert Xu
2008-07-31 12:37               ` Lennert Buytenhek
2008-07-31 12:59                 ` Herbert Xu
2008-08-03  8:23                   ` David Miller
2008-07-31  7:34       ` Ilpo Järvinen
2008-07-31  9:50         ` Lennert Buytenhek
2008-07-31 10:27           ` Ilpo Järvinen
2008-07-31  2:29     ` Herbert Xu
2008-07-31  2:36       ` Lennert Buytenhek
2008-07-31  3:03         ` Herbert Xu
2008-07-31  6:55           ` Ilpo Järvinen
2008-07-31  9:39             ` Lennert Buytenhek
2008-07-31 10:14           ` Lennert Buytenhek
2008-07-31 10:16             ` David Miller
2008-07-31 12:25               ` Lennert Buytenhek
2008-07-31 12:35                 ` David Miller
2008-07-31 13:19                   ` Ben Hutchings
2008-07-31 13:27                     ` Herbert Xu
2008-08-03  8:19                       ` David Miller
2008-08-03  8:55                         ` Herbert Xu
2008-08-07  6:07                           ` David Miller
2008-08-07  6:15                             ` Herbert Xu
2008-09-12  4:08                               ` David Miller
2008-08-07 11:50                             ` Lennert Buytenhek
2008-08-07 20:32                             ` Rick Jones [this message]
2008-08-07 22:44                               ` David Miller
2008-07-31 17:00 ` Rick Jones
2008-07-31 17:45   ` Lennert Buytenhek

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=489B5BC5.3030600@hp.com \
    --to=rick.jones2@hp.com \
    --cc=akarkare@marvell.com \
    --cc=bhutchings@solarflare.com \
    --cc=buytenh@wantstofly.org \
    --cc=dale@farnsworth.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=nico@cam.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).