From: "David S. Miller" <davem@redhat.com>
To: johnip@sgi.com
Cc: ak@suse.de, modica@sgi.com, netdev@oss.sgi.com,
jgarzik@pobox.com, jes@sgi.com
Subject: Re: Tigon3 5701 PCI-X recv performance problem
Date: Mon, 13 Oct 2003 12:51:56 -0700 [thread overview]
Message-ID: <20031013125156.63c3be24.davem@redhat.com> (raw)
In-Reply-To: <3F8B02D2.4020007@sgi.com>
On Mon, 13 Oct 2003 14:53:54 -0500
John Partridge <johnip@sgi.com> wrote:
> Could we create a module argument like "do_5701_align" and just give it a -1
> default which does NOT do the copy but if we give the arg 1, 0, whatever it
> DOES to the copy to align the buffs ?
Absolutely not, we're not going to put super-hacky module parameters
into the driver just because you guys don't want to create and use the
CONFIG_UNALIGNED_EXPENSIVE config option needed to fix this properly.
> That way all the default comiles work and no CONFIG option for people
> who compile all defaults and don't want to re compile the kernel for
> this issue.
>
> Is that acceptable ?
No it's not.
When you add this new config option, and set it on ia64, the only
thing that will need to be rebuilt is the tg3 driver, no other thing
in the entire kernel tree should trigger a dependency on this new
config option.
I don't understand why at all you guys are trying to avoid fixing this
the proper way, you will meet only resistence from me if you continue
doing that :)
next prev parent reply other threads:[~2003-10-13 19:51 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
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 [this message]
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=20031013125156.63c3be24.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=jes@sgi.com \
--cc=jgarzik@pobox.com \
--cc=johnip@sgi.com \
--cc=modica@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).