public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Laurie Gellatly <laurie.gellatly@netic.com>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: "ecos-discuss@sources.redhat.com" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Re: How to use IP/UDP/TCP checksum offload HW?
Date: Tue, 07 Jun 2011 02:18:00 -0000	[thread overview]
Message-ID: <D257F904-78F1-4789-9F4B-FFEB1A12DA56@netic.com> (raw)
In-Reply-To: <isjt0v$req$1@dough.gmane.org>



On 07/06/2011, at 10:57 AM, Grant Edwards <grant.b.edwards@gmail.com> wrote:

> On 2011-06-07, Laurie Gellatly <laurie.gellatly@netic.com> wrote:
> 
>> I tried to enable this before without success.
> 
> Ah yes, I saw your (unanswered) post from a few years back asking
> about this.  I was hoping there had been some progress since then.
> 
>> I agree that its a waste of processor time when it can be performed
>> in hardware.
> 
> The last time I did some profiling, IP checksum calculation was a
> pretty significant bottleneck for TCP throughput.  Back in the NetBSD
> stack days, I got about a 20% improvement in throughput by writing my
> own assembly-language IP checksum routine for ARM7.  The FreeBSD C
> implementation and more recent versions of gcc do almost as well as
> hand-tuned assembly, but it's still a big percentage of CPU usage in
> TCP communications -- and it will be even worse now that I have a chip
> that does scatter-gather DMA.  A part for US $4 that has IP checksum
> offloading and scatter-gather DMA.  Back when I was a new grad...
> 
>> Must we look at the latest BSD code to see how to implement this?
> 
> Maybe.  Or there might be a simpler way to do it.  I would guess that
> the current FreeBSD has an API to configure this on a per-interface
> basis at run-time.
> 
> If we can assume that there is only one external interface, then we
> don't need any API or runtime checks, just a few strategic #if/#endif
> pairs and some CDL to control them.
> 
> -- 
> Grant
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
So how do we progress this?
Should we offline exchange the mods we've each tried (code and CDL)?

...Laurie:{)

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2011-06-07  2:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 19:35 [ECOS] " Grant Edwards
2011-06-07  0:14 ` Laurie Gellatly
2011-06-07  0:57   ` [ECOS] " Grant Edwards
2011-06-07  2:18     ` Laurie Gellatly [this message]
2011-06-07  8:55       ` Ilija Kocho
2011-06-07 14:42         ` Grant Edwards
2011-06-07 16:06           ` Jay Foster
2011-06-07 16:46           ` Ilija Kocho
2011-06-07 19:48             ` John Dallaway
2011-06-07 20:17               ` Laurie Gellatly
2011-07-06 19:17                 ` Ilija Kocho
2011-07-08 11:37                   ` Laurie Gellatly
2011-06-07 20:27               ` Ilija Kocho
     [not found]               ` <34195.33997444$1307477887@news.gmane.org>
2011-06-07 20:29                 ` Grant Edwards
2011-06-07 20:32                   ` Ilija Kocho

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=D257F904-78F1-4789-9F4B-FFEB1A12DA56@netic.com \
    --to=laurie.gellatly@netic.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=grant.b.edwards@gmail.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).