From: "David S. Miller" <davem@redhat.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Zerocopy implementation issues
Date: Sun, 29 Apr 2001 04:06:16 -0700 (PDT) [thread overview]
Message-ID: <15083.62888.860815.889046@pizda.ninka.net> (raw)
In-Reply-To: <20010429113122.E30243@flint.arm.linux.org.uk>
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> <20010429113122.E30243@flint.arm.linux.org.uk>
Russell King writes:
> Or am I missing something?
csum_block_*() has nothing to do with checksumming buffers, it 2's
complement adds two integers passed as arguments based upon the offset
of one of the buffers (this decides if one of the csums needs to be
byte swapped before the 2's complement addition to get a correct
result).
That was the point of my mail, the last_byte_was_odd code
had nothing to do with what your checksum code needs to be
doing, never did and never will. Your premise was that the
last_byte_was_odd code "proved" that the csum_partial_copy
destination buffer could not be byte aligned, and I tried
to show that the last_byte_was_odd code had nothing to do
with whether that was allowed or not.
Your csum_partial_copy*() code needs to handle unaligned
destination buffers, period.
I understand that you are frustruated about this and it
requires you to touch some delicate assembly. But I'm
going to be blunt and say "tough", because everyone has
to implement this correctly. Just do it and get it
over with.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-04-29 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 23:52 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
2001-04-29 11:06 ` David S. Miller [this message]
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=15083.62888.860815.889046@pizda.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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®