From: Stephen Hemminger <shemminger@osdl.org>
To: "Haruki Dai-r35557" <Dai.Haruki@freescale.com>
Cc: <netdev@vger.kernel.org>,
"Fleming Andy-afleming" <afleming@freescale.com>,
"Kumar Gala" <galak@kernel.crashing.org>,
"Haruki Dai-r35557" <Dai.Haruki@freescale.com>
Subject: Re: [PATCH] Gianfar SKB Recycling Support
Date: Fri, 19 May 2006 10:47:57 -0700 [thread overview]
Message-ID: <20060519104757.41a5da9a@localhost.localdomain> (raw)
In-Reply-To: <18AEF66AFDF06F4CAAA1D419D000FD33524B79@az33exm24.fsl.freescale.net>
On Wed, 17 May 2006 15:45:14 -0700
"Haruki Dai-r35557" <Dai.Haruki@freescale.com> wrote:
> This patch improves the IP forwarding throughput of
> the Freescale TSEC/eTSEC Gianfar driver. By recycling
> the Socket buffer and Data buffer, reduce the unnecessary
> memory allocation and de-allocation in the forwarding
> processing chain.
>
> Signed-off-by: Dai Haruki <dai.haruki@freescale.com>
> Signed-off-by: Andy Fleming <afleming@freescale.com>
>
In case the general impression wasn't clear from the earlier comments.
This patch is an interesting benchmark tweak, but unlikely to ever
make it into the mainline kernel. The kernel needs to be a general
purpose system and deal with multiple types of hardware and resource
control.
But don't give up looking at performance. If you can find ways to
speed up the overall socket buffer handling without breaking existing
semantics; then the patches would be positively received.
next prev parent reply other threads:[~2006-05-19 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 22:45 [PATCH] Gianfar SKB Recycling Support Haruki Dai-r35557
2006-05-17 22:49 ` Stephen Hemminger
2006-05-17 22:55 ` Andi Kleen
2006-05-19 17:47 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-18 2:01 Haruki Dai-r35557
2006-05-18 10:11 ` Andi Kleen
2006-05-18 2:03 Haruki Dai-r35557
2006-05-22 1:38 Haruki Dai-r35557
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=20060519104757.41a5da9a@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=Dai.Haruki@freescale.com \
--cc=afleming@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).