From: Nivedita Singhvi <niv@us.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jon Mason <jdmason@us.ibm.com>, shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH] Ethernet Bridging: Enable Hardware Checksumming
Date: Thu, 19 May 2005 08:10:13 -0700 [thread overview]
Message-ID: <428CAC55.4000202@us.ibm.com> (raw)
In-Reply-To: <E1DYayB-0005Sk-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
> Jon Mason <jdmason@us.ibm.com> wrote:
>
>>checksum and scatter gather as features of the bridge device. In the
>>case that the physical ethernet device does not support scatter
>>gather or hardware checksum, dev_queue_xmit() will check the
>>dev->features and do the necessary linearization and calculate the
>>checksum.
>
>
> Unfortunately skb_linearize is a lot more expensive than not
> generating the non-linear skb's in the first place.
>
> So this is going to hurt people using the bridge devices over
> physical devices that don't support SG.
Fair point - though I would argue that devices that
support SG are much more common now - so optimizing
for the more common case might be preferable - since
people using bridging with devices that support
checksum offload are taking quite a hit when they
do bridging - perhaps this could be a conditional?
thanks,
Nivedita
next prev parent reply other threads:[~2005-05-19 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 23:53 [PATCH] Ethernet Bridging: Enable Hardware Checksumming Jon Mason
2005-05-19 0:03 ` Nivedita Singhvi
2005-05-19 5:00 ` David S. Miller
2005-05-19 15:13 ` Nivedita Singhvi
2005-05-19 20:34 ` Stephen Hemminger
2005-05-19 2:41 ` Herbert Xu
2005-05-19 15:10 ` Nivedita Singhvi [this message]
2005-05-19 18:51 ` David S. Miller
2005-05-19 20:43 ` Nivedita Singhvi
2005-05-19 20:33 ` Stephen Hemminger
2005-05-19 21:48 ` David S. Miller
2005-05-19 23:23 ` Jon Mason
2005-05-19 23:36 ` David S. 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=428CAC55.4000202@us.ibm.com \
--to=niv@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jdmason@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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 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.