From: Rick Jones <rick.jones2@hp.com>
To: avorontsov@ru.mvista.com
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
Andy Fleming <afleming@freescale.com>,
Li Yang <leoli@freescale.com>, David Miller <davem@davemloft.net>,
Lennert Buytenhek <buytenh@marvell.com>
Subject: Re: [PATCH] ucc_geth: Add support for skb recycling
Date: Tue, 07 Jul 2009 13:46:54 -0700 [thread overview]
Message-ID: <4A53B43E.4010905@hp.com> (raw)
In-Reply-To: <20090707203712.GA11157@oksana.dev.rtsoft.ru>
Anton Vorontsov wrote:
> On Tue, Jul 07, 2009 at 11:47:38AM -0700, Rick Jones wrote:
>>Admittedly, all the world is not TCP, but a big chunk is, so are you
>>likely to have reference counts go to zero on the tx queue for
>>anything other than small standalone TCP ACK segments?
>
>
> That's a generic question wrt skb recycling, right? Whether we can
> always recycle transmitted skbs. No, sometimes (or mostly) we can't.
>
> Initially, I was quite puzzled by this support... looking at how
> gianfar driver works (it has the same support as of 0fd56bb5be6455d0),
> I noticed that skb_recycle_check() always returns 0, and so we
> don't recycle the skbs.
>
> Though, things change when the kernel starts packets forwarding,
> *then* skb recycling path actually triggers.
>
> Lennert (skb recycling author) hints us that the gain is indeed
> in forwarding/routing workload:
>
> http://kerneltrap.org/mailarchive/linux-netdev/2008/9/28/3433514
>
>
> Hope I understood everything correctly. :-)
Given the text reads:
This gives a nice increase in the maximum loss-free packet forwarding
rate in routing workloads.
Your understanding is probably correct. Might have been "nice" :) to get a
definition of a "nice increase" though :)
rick jones
next prev parent reply other threads:[~2009-07-07 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 18:38 [PATCH] ucc_geth: Add support for skb recycling Anton Vorontsov
2009-07-07 18:47 ` Rick Jones
2009-07-07 20:37 ` Anton Vorontsov
2009-07-07 20:46 ` Rick Jones [this message]
2009-07-08 2:23 ` David Miller
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=4A53B43E.4010905@hp.com \
--to=rick.jones2@hp.com \
--cc=afleming@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=buytenh@marvell.com \
--cc=davem@davemloft.net \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.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).