public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "David S. Miller" <davem@redhat.com>,
	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 21:28:16 +0000	[thread overview]
Message-ID: <20011218212816.G13126@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20011218.131155.91757544.davem@redhat.com> <Pine.LNX.4.33L.0112181923030.28489-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0112181923030.28489-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Tue, Dec 18, 2001 at 07:24:41PM -0200

On Tue, Dec 18, 2001 at 07:24:41PM -0200, Rik van Riel wrote:
> On Tue, 18 Dec 2001, David S. Miller wrote:
> > Not necessarily Russell.  You have even told us on several occaisions
> > that the older ARMs simply cannot fix up unaligned loads/stores in
> > fact.
> 
> 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's actually not worth it; these "older ARMs" I believe we can safely
drop from our sights - it has been my intention throughout 2.4 to drop
them out when 2.5 came around.  The problem is that there are people
who do want still use antequated machines, but they can look after
the problems that entails themselves IMHO. 8)

So, as far as 2.5 is concerned, consider all ARMs capable of handling
mis-aligned accesses via a fault handler.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-12-18 21:31 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 [this message]
2001-12-18 21:33             ` David S. Miller
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=20011218212816.G13126@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=Mika.Liljeberg@nokia.com \
    --cc=Mika.Liljeberg@welho.com \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --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