From: Steve Modica <modica@sgi.com>
To: johnip@sgi.com
Cc: "David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com, jgarzik@pobox.com, jes@sgi.com
Subject: Re: Tigon3 5701 PCI-X recv performance problem
Date: Wed, 08 Oct 2003 14:11:47 -0500 [thread overview]
Message-ID: <3F846173.9090107@sgi.com> (raw)
In-Reply-To: <3F845F61.9080002@sgi.com>
I think it'd be better to create some macro like this:
#ifdef FORCE_SKB_ALIGNMENT
# define SKB_COPY_CHECK(len) len > RX_COPY_THRESHOLD && tp->rx_offset == 2
#else
# define SKB_COPY_CHECK(len) len > RX_COPY_THRESHOLD
#endif
Then replace the code in the if with the new macro. We can define
FORCE_SKB_ALIGNMENT in our build environment as can others if necessary.
otherwise, everyone does what they did before.
Steve
John Partridge wrote:
> OK, fair enough, you mean like :-
>
> #if defined(__ia64__)
> if (len > RX_COPY_THRESHOLD && tp->rx_offset == 2) {
> #else
> if (len > RX_COPY_THRESHOLD) {
> #endif
>
>
>
> David S. Miller wrote:
>
>> On Wed, 08 Oct 2003 12:52:57 -0500
>> John Partridge <johnip@sgi.com> wrote:
>>
>>
>>> Not too much different
>>
>>
>>
>> The problem is that your change is arch-dependant yet you make it
>> run on all platforms.
>>
>> On x86 we don't want to do what your change is doing, the unaligned
>> accesses are cheap enough.
>>
>> We need to abstract this, probably in the same way it is done in
>> the Tulip and other drivers which have similar issues.
>
>
--
Steve Modica
work: 651-683-3224
MTS-Technical Lead
"Give a man a fish, and he will eat for a day, hit him with a fish and
he leaves you alone" - me
next prev parent reply other threads:[~2003-10-08 19:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 17:12 Tigon3 5701 PCI-X recv performance problem John Partridge
2003-10-08 17:10 ` David S. Miller
2003-10-08 17:52 ` John Partridge
2003-10-08 18:26 ` David S. Miller
2003-10-08 19:02 ` John Partridge
2003-10-08 19:11 ` Steve Modica [this message]
2003-10-08 19:15 ` David S. Miller
2003-10-08 18:21 ` Steve Modica
2003-10-08 18:29 ` David S. Miller
2003-10-08 18:37 ` Andi Kleen
2003-10-08 19:22 ` David S. Miller
2003-10-08 20:22 ` Andi Kleen
2003-10-08 20:24 ` David S. Miller
2003-10-08 20:33 ` Andi Kleen
2003-10-08 20:32 ` David S. Miller
2003-10-08 20:46 ` Andi Kleen
2003-10-08 20:50 ` David S. Miller
2003-10-10 19:05 ` Steve Modica
2003-10-10 19:20 ` Andi Kleen
2003-10-11 13:17 ` Steve Modica
2003-10-11 13:19 ` Andi Kleen
2003-10-11 17:50 ` David S. Miller
2003-10-13 19:53 ` John Partridge
2003-10-13 19:51 ` David S. Miller
2003-10-14 16:49 ` John Partridge
2003-10-14 16:53 ` David S. Miller
2003-11-11 1:24 ` John Partridge
2003-11-11 2:29 ` David S. Miller
2003-11-11 20:04 ` John Partridge
2003-11-11 20:24 ` David S. Miller
2003-11-11 21:26 ` John Partridge
2003-11-11 21:32 ` Jeff Garzik
2003-12-03 22:11 ` John Partridge
2003-11-11 21:39 ` John Partridge
2003-11-11 23:09 ` David S. Miller
2003-11-11 23:53 ` Andi Kleen
2003-11-12 1:46 ` John Partridge
2003-11-12 6:19 ` Andi Kleen
2003-11-12 7:05 ` Jeff Garzik
2003-11-12 15:32 ` John Partridge
2003-11-12 15:43 ` Christoph Hellwig
2003-11-11 20:25 ` David S. Miller
2003-11-11 20:57 ` Jeff Garzik
2003-10-14 18:47 ` John Partridge
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=3F846173.9090107@sgi.com \
--to=modica@sgi.com \
--cc=davem@redhat.com \
--cc=jes@sgi.com \
--cc=jgarzik@pobox.com \
--cc=johnip@sgi.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).