From: "gis88530" <gis88530@cis.nctu.edu.tw>
To: <root@chaos.analogic.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: skbuff.h
Date: Mon, 9 Apr 2001 23:46:58 +0800 [thread overview]
Message-ID: <018601c0c10c$50f5d3b0$ae58718c@cis.nctu.edu.tw> (raw)
In-Reply-To: <Pine.LNX.3.95.1010409102624.12657A-100000@chaos.analogic.com>
Thanks a lot.
Do you know the purpose of csum_partial( ) function?
I can't find out it source code.
I can't believe that I have discovered an area where an
improvement in performance. Maybe I loss some thing.
Cheers,
Tom
> On Mon, 9 Apr 2001, nctucis wrote:
>
> > Hi,
> >
> > I use 2.2.16 kernel.
> > I found that there is a sk_buff structure in
> > "/usr/src/linux/include/linux/skbuff.c", and
> > there is a variable "unsigned in csum;" in
> > the sk_buff structure.
> >
> > I want to know this checksum check what information.
> > Could you give me a hand, please?
> >
> > -=-=-=-=-=-=-=-
> > In fact, I found 64byte and 1518byte UDP packet waste different
> > time to do masquerade(ip_fw_masquerade).
> > Many books say NAT just modify header fields, so it should no
> > different between small and big packet size.
> > I guess the different time due to csum_partial(h.raw, doff, sum)
> > in ip_fw_masquerade(). Right? Thanks a lot.
> > (But I can't find out source code of this function.)
> >
> > Cheers,
> > Tom
>
> TCP/IP packets contain a checksum. The checksum is defined by the
> standards. Linux checksums the IP packets in two ways, the first
> is obvious, the second is the 'csum_partial_copy_generic' in
> ../linux/arch/i386/lib/checksum.S.
>
> NAT, because it modifies the IP packet, must also modify the
> checksum. However, the checksum is in the IP header so your
> 'books' are correct. FYI, since the checksum is known, the
> IP address is known, and the standard is known. It is not
> necessary to re-checksum the entire packet to produce a new
> checksum after modification of some of the checksummed data
> (IP address).
>
> I think Linux recalculates the entire checksum over again so
> you may have discovered an area where an improvement in performance
> could be obtained.
>
>
> Cheers,
> Dick Johnson
>
> Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
>
> "Memory is like gasoline. You use it up when you are running. Of
> course you get it all back when you reboot..."; Actual explanation
> obtained from the Micro$oft help desk.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-04-09 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 13:48 skbuff.h nctucis
2001-04-09 14:36 ` skbuff.h Richard B. Johnson
2001-04-09 15:46 ` gis88530 [this message]
2001-04-09 15:59 ` skbuff.h Richard B. Johnson
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='018601c0c10c$50f5d3b0$ae58718c@cis.nctu.edu.tw' \
--to=gis88530@cis.nctu.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®