From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Paul P Komkoff Jr <i@stingr.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MTU vlan-related patch for tulip (2.4.x)
Date: Mon, 10 Dec 2001 15:00:45 -0500 [thread overview]
Message-ID: <3C15146D.BA780B43@mandrakesoft.com> (raw)
In-Reply-To: <20011210225759.B11450@stingr.net>
Paul P Komkoff Jr wrote:
> diff -urN linux-2.4.9-ac10-novlan/drivers/net/tulip/tulip.h linux-2.4.9-ac10/drivers/net/tulip/tulip.h
> --- linux-2.4.9-ac10-novlan/drivers/net/tulip/tulip.h Wed Jun 20 22:19:02 2001
> +++ linux-2.4.9-ac10/drivers/net/tulip/tulip.h Mon Sep 10 18:42:27 2001
> @@ -264,7 +264,7 @@
>
> #define MEDIA_MASK 31
>
> -#define PKT_BUF_SZ 1536 /* Size of each temporary Rx buffer. */
> +#define PKT_BUF_SZ 1540 /* Size of each temporary Rx buffer. */
>
> #define TULIP_MIN_CACHE_LINE 8 /* in units of 32-bit words */
>
> diff -urN linux-2.4.9-ac10-novlan/drivers/net/tulip/tulip_core.c linux-2.4.9-ac10/drivers/net/tulip/tulip_core.c
> --- linux-2.4.9-ac10-novlan/drivers/net/tulip/tulip_core.c Mon Sep 10 18:50:47 2001
> +++ linux-2.4.9-ac10/drivers/net/tulip/tulip_core.c Mon Sep 10 18:39:59 2001
> @@ -59,7 +59,7 @@
> #if defined(__alpha__) || defined(__arm__) || defined(__hppa__) \
> || defined(__sparc_) || defined(__ia64__) \
> || defined(__sh__) || defined(__mips__)
> -static int rx_copybreak = 1518;
> +static int rx_copybreak = 1522;
> #else
> static int rx_copybreak = 100;
> #endif
I haven't added it to mainline because of these two patches... I want
to fully analyze their affects before potentially shifting allocation
patterns particularly.
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-12-10 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 19:57 [PATCH] MTU vlan-related patch for tulip (2.4.x) Paul P Komkoff Jr
2001-12-10 20:00 ` Jeff Garzik [this message]
2001-12-10 20:07 ` Jeff Garzik
2001-12-10 20:22 ` Ben Greear
2001-12-10 22:37 ` Benjamin LaHaise
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=3C15146D.BA780B43@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=i@stingr.net \
--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