From: Claudiu Manoil <claudiu.manoil@freescale.com>
To: Matei Pavaluca <matei.pavaluca@freescale.com>, <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v2 3/3] gianfar: Implement PAUSE frame generation support
Date: Thu, 23 Oct 2014 12:36:55 +0300 [thread overview]
Message-ID: <5448CC37.6040300@freescale.com> (raw)
In-Reply-To: <1414055930-10331-1-git-send-email-matei.pavaluca@freescale.com>
On 10/23/2014 12:18 PM, Matei Pavaluca wrote:
> The hardware can automatically generate pause frames when the number
> of free buffers drops under a certain threshold, but in order to do this,
> the address of the last free buffer needs to be written to a specific
> register for each RX queue.
>
> This has to be done in 'gfar_clean_rx_ring' which is called for each
> RX queue. In order not to impact performance, by adding a register write
> for each incoming packet, this operation is done only when the PAUSE frame
> transmission is enabled.
>
> Whenever the link is readjusted, this capability is turned on or off.
>
> Signed-off-by: Matei Pavaluca <matei.pavaluca@freescale.com>
> ---
>
> v2:
> - Added unlikely() in 'gfar_clean_rx_ring'
> - Removed some unused variables
Acked-by: Claudiu Manoil <claudiu.manoil@freescale.com>
next prev parent reply other threads:[~2014-10-23 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 9:18 [PATCH net-next v2 3/3] gianfar: Implement PAUSE frame generation support Matei Pavaluca
2014-10-23 9:36 ` Claudiu Manoil [this message]
2014-10-23 19:23 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-10-27 8:42 [PATCH net-next v2 1/3] Add flow control support flags to gianfar's capabilities Matei Pavaluca
2014-10-27 8:42 ` [PATCH net-next v2 3/3] gianfar: Implement PAUSE frame generation support Matei Pavaluca
2014-10-29 18:34 ` 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=5448CC37.6040300@freescale.com \
--to=claudiu.manoil@freescale.com \
--cc=davem@davemloft.net \
--cc=matei.pavaluca@freescale.com \
--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 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.