From: "David S. Miller" <davem@davemloft.net>
To: akpm@osdl.org
Cc: phdm@macqel.be, linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: PATCH : ppp + big-endian = kernel crash
Date: Sun, 29 May 2005 20:11:04 -0700 (PDT) [thread overview]
Message-ID: <20050529.201104.59476605.davem@davemloft.net> (raw)
In-Reply-To: <20050529195245.33f36253.akpm@osdl.org>
From: Andrew Morton <akpm@osdl.org>
Date: Sun, 29 May 2005 19:52:45 -0700
> > All these patches to PPP and friends are merely papering over the
> > larger problem.
>
> It's not a thing we want to do in the general case, sure. But it's
> reasonable to identify those bits of net code which the nommu people care
> about and look to see if there's some sane workaround to get them going.
>
> Otherwise, things like PPP will simply unavailable to some architectures...
Some time ago there was a proposal that would allow appropriate
handling of these sorts of things.
Accessors to packet headers would go through a macro, and this
along with some other defines would allow an architecture to
decide between two schemes:
1) Use normal loads and stores, let trap handler take care of
unaligned cases.
2) Use something akin to get_unaligned(), no trap handler stuff.
Sure, to make things faster we can do something like this PPP
patch, but it needs lots of work, first of all you need to
replace this:
for ( ... )
p[i-1] = p[i];
stuff with a proper memmove() call.
next prev parent reply other threads:[~2005-05-30 3:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 19:48 PATCH : ppp + big-endian = kernel crash Philippe De Muyter
2005-05-29 20:52 ` David S. Miller
2005-05-29 21:38 ` Philippe De Muyter
2005-05-29 21:55 ` David S. Miller
2005-05-30 2:52 ` Andrew Morton
2005-05-30 3:11 ` David S. Miller [this message]
2005-06-01 15:26 ` Philippe De Muyter
2005-05-30 10:22 ` Andi Kleen
2005-05-30 13:01 ` cutaway
2005-05-30 7:16 ` Giuliano Pochini
-- strict thread matches above, loose matches on Subject: below --
2005-05-30 14:05 Greg Ungerer
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=20050529.201104.59476605.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=uclinux-dev@uclinux.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