All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>
Cc: davem@davemloft.net, stephen.hemminger@vyatta.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH] [NET 2.6.26]: Add per-connection option to set max TSO frame   size
Date: Fri, 29 Feb 2008 21:46:50 +0100	[thread overview]
Message-ID: <20080229204650.GA2848@ami.dom.local> (raw)
In-Reply-To: <20080228183150.4431.81252.stgit@localhost.localdomain>

PJ Waskiewicz wrote, On 02/28/2008 07:31 PM:
...
> This can be desirable to help tune the bursty nature of TSO on a
> per-adapter basis, where one may have 1 GbE and 10 GbE devices coexisting
> in a system, one running multiqueue and the other not, etc.
> 
> This can also be desirable for devices that cannot support full 64 KB
> TSO's, but still want to benefit from some level of segmentation
> offloading.
...
> +++ b/include/linux/netdevice.h
...
> +	/* for setting kernel sock attribute on TCP connection setup */
> +#define GSO_MAX_SIZE		65536
> +	u32			gso_max_size;

One more, maybe foolish, thrifty idea: do we really need such a
precision here? I don't know those devices, but maybe it would be
enough (for the beginning at least?) to use a few divisors e.g.:

gso_max_size = 65536 >> GSO_MAX_SIZE_SHIFT

Then it seems 3 or 4 bits should be enough for this, and BTW, it looks
like dev->features has 16 bits for various GSO flags, with "a lot" of
free space yet - unless I missed something?

Jarek P.

  parent reply	other threads:[~2008-02-29 20:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 18:31 [PATCH] [NET 2.6.26]: Add per-connection option to set max TSO frame size PJ Waskiewicz
2008-02-29 10:53 ` Jarek Poplawski
2008-02-29 20:46 ` Jarek Poplawski [this message]
2008-02-29 21:11   ` Jarek Poplawski
2008-02-29 23:20   ` [PATCH] [NET 2.6.26]: Add per-connection option to set max TSOframe size Waskiewicz Jr, Peter P
2008-03-01 19:48     ` Jarek Poplawski
  -- strict thread matches above, loose matches on Subject: below --
2008-03-05 17:35 [PATCH] [NET 2.6.26]: Add per-connection option to set max TSO frame size PJ Waskiewicz
2008-03-21 10:45 ` David Miller
2008-02-27 17:26 PJ Waskiewicz
2008-02-28  8:07 ` Jarek Poplawski
2008-02-28  8:29   ` Jarek Poplawski
2008-02-13 11:45 PJ Waskiewicz

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=20080229204650.GA2848@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=stephen.hemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.