From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Cc: edumazet@gmail.com, open list <linux-kernel@vger.kernel.org>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@lists.osuosl.org>,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v3] e1000e: Be drop monitor friendly
Date: Wed, 6 Sep 2017 10:06:39 +0300 [thread overview]
Message-ID: <bdd7d5a3-2004-ad2e-3c09-8198d76acafa@intel.com> (raw)
In-Reply-To: <20170826011424.27251-1-f.fainelli@gmail.com>
On 8/26/2017 04:14, Florian Fainelli wrote:
> e1000e_put_txbuf() can be called from normal reclamation path as well as
> when a DMA mapping failure, so we need to differentiate these two cases
> when freeing SKBs to be drop monitor friendly. e1000e_tx_hwtstamp_work()
> and e1000_remove() are processing TX timestamped SKBs and those should
> not be accounted as drops either.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> Changes in v3:
>
> - differentiate normal reclamation from TX DMA fragment mapping errors
> - removed a few invalid dev_kfree_skb() replacements (those are already
> drop monitor friendly)
>
> Changes in v2:
>
> - make it compile
>
> drivers/net/ethernet/intel/e1000e/netdev.c | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c b/drivers/net/ethernet/intel/e1000e/netdev.c
> index 327dfe5bedc0..cfd21858c095 100644
> --- a/drivers/net/ethernet/intel/e1000e/netdev.c
> +++ b/drivers/net/ethernet/intel/e1000e/netdev.c
> @@ -1071,7 +1071,8 @@ static bool e1000_clean_rx_irq(struct e1000_ring *rx_ring, int *work_done,
> }
>
> static void e1000_put_txbuf(struct e1000_ring *tx_ring,
> - struct e1000_buffer *buffer_info)
> + struct e1000_buffer *buffer_info,
> + bool drop)
> {
> struct e1000_adapter *adapter = tx_ring->adapter;
>
> @@ -1085,7 +1086,10 @@ static void e1000_put_txbuf(struct e1000_ring *tx_ring,
> buffer_info->dma = 0;
> }
> if (buffer_info->skb) {
> - dev_kfree_skb_any(buffer_info->skb);
> + if (drop)
> + dev_kfree_skb_any(buffer_info->skb);
> + else
> + dev_consume_skb_any(buffer_info->skb);
> buffer_info->skb = NULL;
> }
> buffer_info->time_stamp = 0;
> @@ -1199,7 +1203,7 @@ static void e1000e_tx_hwtstamp_work(struct work_struct *work)
> wmb(); /* force write prior to skb_tstamp_tx */
>
> skb_tstamp_tx(skb, &shhwtstamps);
> - dev_kfree_skb_any(skb);
> + dev_consume_skb_any(skb);
> } else if (time_after(jiffies, adapter->tx_hwtstamp_start
> + adapter->tx_timeout_factor * HZ)) {
> dev_kfree_skb_any(adapter->tx_hwtstamp_skb);
> @@ -1254,7 +1258,7 @@ static bool e1000_clean_tx_irq(struct e1000_ring *tx_ring)
> }
> }
>
> - e1000_put_txbuf(tx_ring, buffer_info);
> + e1000_put_txbuf(tx_ring, buffer_info, false);
> tx_desc->upper.data = 0;
>
> i++;
> @@ -2421,7 +2425,7 @@ static void e1000_clean_tx_ring(struct e1000_ring *tx_ring)
>
> for (i = 0; i < tx_ring->count; i++) {
> buffer_info = &tx_ring->buffer_info[i];
> - e1000_put_txbuf(tx_ring, buffer_info);
> + e1000_put_txbuf(tx_ring, buffer_info, false);
> }
>
> netdev_reset_queue(adapter->netdev);
> @@ -5614,7 +5618,7 @@ static int e1000_tx_map(struct e1000_ring *tx_ring, struct sk_buff *skb,
> i += tx_ring->count;
> i--;
> buffer_info = &tx_ring->buffer_info[i];
> - e1000_put_txbuf(tx_ring, buffer_info);
> + e1000_put_txbuf(tx_ring, buffer_info, true);
> }
>
> return 0;
> @@ -7411,7 +7415,7 @@ static void e1000_remove(struct pci_dev *pdev)
> if (adapter->flags & FLAG_HAS_HW_TIMESTAMP) {
> cancel_work_sync(&adapter->tx_hwtstamp_work);
> if (adapter->tx_hwtstamp_skb) {
> - dev_kfree_skb_any(adapter->tx_hwtstamp_skb);
> + dev_consume_skb_any(adapter->tx_hwtstamp_skb);
> adapter->tx_hwtstamp_skb = NULL;
> }
> }
i am ok with this patch
next prev parent reply other threads:[~2017-09-06 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 1:14 [PATCH net-next v3] e1000e: Be drop monitor friendly Florian Fainelli
2017-09-06 7:06 ` Neftin, Sasha [this message]
2017-09-14 23:54 ` [Intel-wired-lan] " Brown, Aaron F
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=bdd7d5a3-2004-ad2e-3c09-8198d76acafa@intel.com \
--to=sasha.neftin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.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).