From: "David S. Miller" <davem@redhat.com>
To: riel@conectiva.com.br
Cc: rmk@arm.linux.org.uk, kuznet@ms2.inr.ac.ru,
Mika.Liljeberg@welho.com, Mika.Liljeberg@nokia.com,
linux-kernel@vger.kernel.org, sarolaht@cs.helsinki.fi
Subject: Re: ARM: Re: TCP LAST-ACK state broken in 2.4.17-pre2 [NEW DATA]
Date: Tue, 18 Dec 2001 13:33:38 -0800 (PST) [thread overview]
Message-ID: <20011218.133338.122061979.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0112181923030.28489-100000@duckman.distro.conectiva>
In-Reply-To: <20011218.131155.91757544.davem@redhat.com> <Pine.LNX.4.33L.0112181923030.28489-100000@duckman.distro.conectiva>
From: Rik van Riel <riel@conectiva.com.br>
Date: Tue, 18 Dec 2001 19:24:41 -0200 (BRST)
Then the problem will have to be fixed elsewhere, maybe
by having the networking code do explicit unaligned
accesses through some macro which defaults to a normal
access on other systems ?
It is a port requirement to fix up such accesses. It has always been
a port requirement to fix up such accesses, and it isn't going to
change.
If I fix up TCP options, I'd have to fixup every access to every
single networking header in the entire stack because "protocol in
protocol" cases can cause unaligned accesses to happen just about any
place.
next prev parent reply other threads:[~2001-12-18 21:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 9:33 TCP LAST-ACK state broken in 2.4.17-pre2 [NEW DATA] Mika.Liljeberg
2001-12-18 18:37 ` kuznet
2001-12-18 20:21 ` Mika Liljeberg
2001-12-18 20:28 ` David S. Miller
2001-12-18 20:29 ` ARM: " kuznet
2001-12-18 20:52 ` Mika Liljeberg
2001-12-18 21:08 ` David S. Miller
2001-12-18 21:03 ` Russell King
2001-12-18 21:11 ` David S. Miller
2001-12-18 21:14 ` Russell King
2001-12-18 21:15 ` David S. Miller
2001-12-18 21:27 ` Mika Liljeberg
2001-12-18 21:24 ` Rik van Riel
2001-12-18 21:28 ` Russell King
2001-12-18 21:33 ` David S. Miller [this message]
2001-12-20 7:31 ` Stevie O
2001-12-20 7:40 ` David S. Miller
2001-12-20 7:51 ` Stevie O
2001-12-20 8:58 ` Russell King
2001-12-20 9:01 ` Russell King
2001-12-20 10:22 ` David Weinehall
2002-01-02 19:52 ` Mike Touloumtzis
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 9:10 ARM: " Mika.Liljeberg
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=20011218.133338.122061979.davem@redhat.com \
--to=davem@redhat.com \
--cc=Mika.Liljeberg@nokia.com \
--cc=Mika.Liljeberg@welho.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rmk@arm.linux.org.uk \
--cc=sarolaht@cs.helsinki.fi \
/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