From: Russell King <rmk@arm.linux.org.uk>
To: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Zerocopy implementation issues
Date: Sun, 29 Apr 2001 11:31:22 +0100 [thread overview]
Message-ID: <20010429113122.E30243@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010429005206.J21792@flint.arm.linux.org.uk> <15083.40318.158099.137018@pizda.ninka.net> <20010429072342.B30041@flint.arm.linux.org.uk> <15083.52835.992666.897323@pizda.ninka.net> <20010429101739.D30243@flint.arm.linux.org.uk>
In-Reply-To: <20010429101739.D30243@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Sun, Apr 29, 2001 at 10:17:39AM +0100
On Sun, Apr 29, 2001 at 10:17:39AM +0100, Russell King wrote:
> On Sun, Apr 29, 2001 at 01:18:43AM -0700, David S. Miller wrote:
> > Occaisionally I find that sparc64 is making a gross error or invalid
> > assumption, and I accept this and fix it up.
>
> Ok, I see precisely what's going on here now, shame you didn't explain
> about these csum_add stuff in your first mail on this subject, and
> we could've saved going down this path.
>
> I'll fix up the ARM code, but its not going to be nice.
David,
Would it be acceptable to have csum_block_* in the architecture
specific code?
Firstly, architecture specific code can optimise them more
efficiently, and secondly it will prevent checksum rotations in
the architecture specific code which will only get undone by
the csum_block_* code.
Or am I missing something?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-04-29 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 23:52 Zerocopy implementation issues Russell King
2001-04-29 4:50 ` David S. Miller
[not found] ` <20010429072342.B30041@flint.arm.linux.org.uk>
[not found] ` <15083.52835.992666.897323@pizda.ninka.net>
2001-04-29 8:39 ` Russell King
2001-04-29 9:17 ` Russell King
2001-04-29 10:31 ` Russell King [this message]
2001-04-29 11:06 ` David S. Miller
2001-04-29 11:18 ` Russell King
2001-04-29 11:32 ` 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=20010429113122.E30243@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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.