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] How to use IP/UDP/TCP checksum offload HW?
Date: Tue, 07 Jun 2011 00:14:00 -0000	[thread overview]
Message-ID: <1478E21E-D36A-4451-9F69-0042CBF57E91@netic.com> (raw)
In-Reply-To: <isja4b$h1e$1@dough.gmane.org>

Hi Grant,
I tried to enable this before without success. I agree that its a waste of processor time when it can be performed in hardware. Must we look at the latest BSD code to see how to implement this?

        ...Laurie:{)


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

> How do you tell the eCos network API that IP/TCP/UDP checksumming is
> handled by hardware?  I've found the if_data.ifi_hwassist field, but
> I'm not positive it really does what I want, and it only seems to
> affect the tx side of the stack.
> 
> Does if_data.ifi_hwassist tell ip_output.c to skil checkums in tx
> packets and let the hardware do it?
> 
> How do you tell the rx side of the stack that it doesn't need to check
> IP, UDP, and TCP checksums (the hardware will discard any packets with
> invalid checksums).
> 
> It seems a shame to not support for HW checksum offloading when it's
> gotten to the point where even a $4 uController has IP checksum
> offloading HW.
> 
> -- 
> Grant Edwards               grant.b.edwards        Yow! Eisenhower!!  Your
>                                  at               mimeograph machine upsets
>                              gmail.com            my stomach!!
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 

--
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  0:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 19:35 Grant Edwards
2011-06-07  0:14 ` Laurie Gellatly [this message]
2011-06-07  0:57   ` [ECOS] " Grant Edwards
2011-06-07  2:18     ` Laurie Gellatly
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=1478E21E-D36A-4451-9F69-0042CBF57E91@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).