public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: James.Bottomley@SteelEye.com
Cc: acme@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: New struct sock_common breaks parisc 64 bit compiles with a misalignment
Date: Sun, 15 Jun 2003 08:23:55 -0700 (PDT)	[thread overview]
Message-ID: <20030615.082355.08334189.davem@redhat.com> (raw)
In-Reply-To: <1055690231.10803.54.camel@mulgrave>

   From: James Bottomley <James.Bottomley@SteelEye.com>
   Date: 15 Jun 2003 10:17:10 -0500
   
   It's not necessary and would, indeed, be detrimental to operation since
   we'd generate alignment traps on almost every encapsulated protocol (at
   several hundred instructions per trap).  If we do this, our network
   performance will tank.

It doesn't happen for all the normal cases, but it does for
things like IP in appletalk and stuff like that.

Please, implement the trap handlers.  Thanks.

  reply	other threads:[~2003-06-15 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10  4:57 New struct sock_common breaks parisc 64 bit compiles with a misalignment James Bottomley
2003-06-10 16:12 ` David S. Miller
2003-06-15 17:09   ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-15 17:06     ` David S. Miller
2003-06-15  6:19 ` David S. Miller
2003-06-15 14:35   ` James Bottomley
2003-06-15 14:35     ` David S. Miller
2003-06-15 15:17       ` James Bottomley
2003-06-15 15:23         ` David S. Miller [this message]
     [not found] <1055687753.10803.28.camel@mulgrave.suse.lists.linux.kernel>
     [not found] ` <20030615.073503.112613460.davem@redhat.com.suse.lists.linux.kernel>
     [not found]   ` <1055690231.10803.54.camel@mulgrave.suse.lists.linux.kernel>
     [not found]     ` <20030615.082355.08334189.davem@redhat.com.suse.lists.linux.kernel>
2003-06-15 15:41       ` Andi Kleen

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=20030615.082355.08334189.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=acme@conectiva.com.br \
    --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