From: Johannes Erdfelt <johannes@erdfelt.com>
To: Andi Kleen <ak@suse.de>
Cc: "Hen, Shmulik" <shmulik.hen@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel memory allocations alignment
Date: Sun, 4 Feb 2001 13:17:54 -0500 [thread overview]
Message-ID: <20010204131753.L22751@sventech.com> (raw)
In-Reply-To: <07E6E3B8C072D211AC4100A0C9C5758302B2711B@hasmsx52.iil.intel.com> <oup66iq8ju2.fsf@pigdrop.muc.suse.de>
In-Reply-To: <oup66iq8ju2.fsf@pigdrop.muc.suse.de>; from Andi Kleen on Sun, Feb 04, 2001 at 06:00:05PM +0100
On Sun, Feb 04, 2001, Andi Kleen <ak@suse.de> wrote:
> "Hen, Shmulik" <shmulik.hen@intel.com> writes:
>
> > Actually yes. We were warned that on IA64 architecture the system will halt
> > when accessing any type of variable via a pointer if the pointer does not
> > contain an aligned address matching that type. Until now we were using a
>
> That will need to be fixed with a handler anyways, the network stack requires
> unaligned accesses. If the IA64 port doesn't handle that it it's buggy and
> trivially remotely crashable.
That ia64 port now supports unaligned accesses in kernel mode. (via the
latest patch)
It was more a debugging aid in the beginning than inability to do.
> Of course it'll always be much faster to use aligned accesses that do not
> need an exception.
Absolutely.
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 16:15 kernel memory allocations alignment Hen, Shmulik
2001-02-04 17:00 ` Andi Kleen
2001-02-04 18:17 ` Johannes Erdfelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-04 14:19 Hen, Shmulik
2001-02-04 15:56 ` Manfred
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=20010204131753.L22751@sventech.com \
--to=johannes@erdfelt.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shmulik.hen@intel.com \
/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