netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: Anton Blanchard <anton@samba.org>
Cc: netdev@oss.sgi.com, davem@redhat.com
Subject: Re: Use NET_IP_ALIGN in acenic
Date: 28 Jul 2004 02:37:25 -0400	[thread overview]
Message-ID: <yq0llh4ab8a.fsf@wildopensource.com> (raw)
In-Reply-To: <20040724174348.GL4556@krispykreme>

>>>>> "Anton" == Anton Blanchard <anton@samba.org> writes:

Anton> Use NET_IP_ALIGN in acenic driver. Also remove the 16 byte
Anton> padding, caches can be anywhere from 16 to 256 bytes and the
Anton> skb should be cacheline aligned already.

Hi Anton,

I don't have any objections to this one, however the main reason for
the 14 byte padding was to 32 bit align the IP header to avoid too
many misaligned loads rather than hitting any cache boundary.

Cheers,
Jes

      parent reply	other threads:[~2004-07-28  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 17:43 Use NET_IP_ALIGN in acenic Anton Blanchard
2004-07-25  5:41 ` David S. Miller
2004-07-28  6:37 ` Jes Sorensen [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=yq0llh4ab8a.fsf@wildopensource.com \
    --to=jes@wildopensource.com \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).