Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Jochen Friedrich <jochen@scram.de>
Cc: mike_phillips@urscorp.com, linux-tr@linuxtr.net,
	HP900 PARISC mailing list <parisc-linux@lists.parisc-linux.org>,
	Randolph Chung <randolph@tausq.org>,
	Matthew Wilcox <willy@debian.org>
Subject: Re: [linux-tr] Re: [parisc-linux] IBM TR patch
Date: Wed, 16 Jan 2002 22:01:30 -0700	[thread overview]
Message-ID: <20020117050130.64F98482D@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Jochen Friedrich <jochen@scram.de> of "Tue, 15 Jan 2002 21:28:13 +0100." <Pine.LNX.4.43.0201152120370.11606-100000@alpha.bocc.de>

Jochen Friedrich wrote:
> Hi Mike,
> I guess the pre-summarisation is there for performance reasons. In 
> particular on older architectures, it's probably faster to copy and 
> calculate the IPv4 checksum in the same step than to copy and checksum in 
> two seperate steps.

I believe it's faster on all archs to do this in one loop.
Assuming one has enough registers to do both operations at the same time.
My assumption is anything that can run linux has enough registers.
(ie ld/st does not collide with xor).

grant

  reply	other threads:[~2002-01-17  5:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 20:10 [linux-tr] Re: [parisc-linux] IBM TR patch mike_phillips
2002-01-15 20:28 ` Jochen Friedrich
2002-01-17  5:01   ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15 20:10 mike_phillips
2002-01-15 20:32 ` Jochen Friedrich
2002-01-15 21:37   ` Alan Cox
2002-01-19 14:39 drequena

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=20020117050130.64F98482D@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=jochen@scram.de \
    --cc=linux-tr@linuxtr.net \
    --cc=mike_phillips@urscorp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=randolph@tausq.org \
    --cc=willy@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox