All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: B05799@freescale.com
Cc: vladz@broadcom.com, netdev@vger.kernel.org, eilong@broadcom.com
Subject: Re: [net-next] bnx2x: Handle Rx and Tx together in NAPI
Date: Mon, 16 Nov 2009 04:24:29 -0800 (PST)	[thread overview]
Message-ID: <20091116.042429.194566531.davem@davemloft.net> (raw)
In-Reply-To: <9F4C7D19E8361D4C94921B95BE08B81B950C11@zin33exm22.fsl.freescale.net>

From: "Kumar Gopalpet-B05799" <B05799@freescale.com>
Date: Mon, 16 Nov 2009 17:26:33 +0530

> In the current implemnetation, the ->poll() function does the cleanup of
> the tx and rx rings of the same device.
> In case of forwarding scenarios (for eg, eth0 --> eth1) we should clean
> the tx ring of eth1 so that the buffers can be reclaimed and they be
> reused for eth0 RX and same is the case for opposite flow. With the
> current implementation there will be a problem for the bidirectional
> flow as a ->poll() function will try to cleanup the rx and tx ring of
> the same device.
> 
> Hence I feel, if we separate out the tx and rx clean ring processes, it
> would be more advantageous as the reclaim process can be more effective.

Eric Dumazet is working on patches to make sure the TX frees
get scheduled on the same CPU as they were transmitted on.

Therefore, you shouldn't try to approximate this in your driver.

  reply	other threads:[~2009-11-16 12:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 10:01 [net-next] bnx2x: Handle Rx and Tx together in NAPI Vladislav Zolotarov
2009-11-16 10:20 ` David Miller
2009-11-16 10:32   ` Kumar Gopalpet-B05799
2009-11-16 10:41     ` David Miller
2009-11-16 11:03       ` Kumar Gopalpet-B05799
2009-11-16 11:05         ` David Miller
2009-11-16 11:56           ` Kumar Gopalpet-B05799
2009-11-16 12:24             ` David Miller [this message]
2009-11-16 11:11   ` Vladislav Zolotarov
2009-11-16 11:24     ` David Miller
2009-11-16 14:47       ` Vladislav Zolotarov
  -- strict thread matches above, loose matches on Subject: below --
2009-11-16 16:05 Vladislav Zolotarov
2009-11-17 12:08 ` 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=20091116.042429.194566531.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=B05799@freescale.com \
    --cc=eilong@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=vladz@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.