From: Arvind Gopalan <arvind_gopalan@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@redhat.com>
Subject: Re: 4 byte mem alignment
Date: Sun, 29 Sep 2002 00:00:21 -0700 (PDT) [thread overview]
Message-ID: <20020929070021.7735.qmail@web14602.mail.yahoo.com> (raw)
In-Reply-To: <20020928.232326.43409659.davem@redhat.com>
Thanks Dave, for confirming my doubt. I have some user
level code that uses raw sockets on
linux. The code ran on several dual PIII x86 machines
without any issues. But since the time we started
running (the same code with no changes) on the dual
x86 xeons, i have seen some wierd corruption issues
with the packets. This kernel already has the patch
for the xeon TLB flush bug. On some of the eth packets
that I dumped, i found that 8 bytes of data being
"copied and inserted"!. As in after a certain offset
into the packet, there would be a sequence of 8 bytes
that would be an exact copy of the 8 bytes that
appeared just before. All other following bytes were
literally shifted down by 8. How can i proceed to
debug this sort of a problem. if its a xeon specific
issue, how can i isolate it?.
Thanks
-Arvind
--- "David S. Miller" <davem@redhat.com> wrote:
> From: Arvind Gopalan <arvind_gopalan@yahoo.com>
> Date: Sat, 28 Sep 2002 23:26:46 -0700 (PDT)
>
> how strong the requirements are for
> copy_to_user().
> does it fault to byte-by-byte mode gracefully
> when
> given a non-4byte aligned buffer?.
>
> The x86 processor handles unaligned memory accesses
> in hw.
>
> On any platform, copy_to_user() must handle any user
> and kernel buffer
> alignment.
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
prev parent reply other threads:[~2002-09-29 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 6:26 Arvind Gopalan
2002-09-29 6:23 ` David S. Miller
2002-09-29 7:00 ` Arvind Gopalan [this message]
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=20020929070021.7735.qmail@web14602.mail.yahoo.com \
--to=arvind_gopalan@yahoo.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®