From: Robert Stonehouse <rstonehouse@solarflare.com>
To: Edward Cree <ecree@solarflare.com>,
Daniel Borkmann <dborkman@redhat.com>
Cc: <davem@davemloft.net>, <nikolay@redhat.com>,
<netdev@vger.kernel.org>, Shradha Shah <sshah@solarflare.com>,
Jon Cooper <jcooper@solarflare.com>,
linux-net-drivers <linux-net-drivers@solarflare.com>
Subject: Re: [PATCH RFC net-next] sfc: add support for skb->xmit_more
Date: Thu, 16 Oct 2014 17:36:24 +0100 [thread overview]
Message-ID: <543FF408.3000808@solarflare.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1410141933500.26972@solarflare.com>
On 14/10/14 19:41, Edward Cree wrote:
> Don't ring the doorbell, and don't do PIO. This will also prevent
> TX Push, because there will be more than one buffer waiting when
> the doorbell is rung.
>
> Signed-off-by: Edward Cree <ecree@solarflare.com>
> ---
>
> @@ -351,8 +343,6 @@ netdev_tx_t efx_enqueue_skb(struct efx_tx_queue *tx_queue, struct sk_buff *skb)
> unsigned short dma_flags;
> int i = 0;
>
> - EFX_BUG_ON_PARANOID(tx_queue->write_count != tx_queue->insert_count);
> -
> if (skb_shinfo(skb)->gso_size)
> return efx_enqueue_skb_tso(tx_queue, skb);
Would it be possible to keep a weaker version of this check i.e.
EFX_BUG_ON_PARANOID(tx_queue->write_count > tx_queue->insert_count);
> @@ -1258,14 +1249,13 @@ static int efx_enqueue_skb_tso(struct efx_tx_queue *tx_queue,
> struct sk_buff *skb)
> {
> struct efx_nic *efx = tx_queue->efx;
> + unsigned int old_insert_count = tx_queue->insert_count;
> int frag_i, rc;
> struct tso_state state;
>
> /* Find the packet protocol and sanity-check it */
> state.protocol = efx_tso_check_protocol(skb);
>
> - EFX_BUG_ON_PARANOID(tx_queue->write_count != tx_queue->insert_count);
> -
> rc = tso_start(&state, efx, skb);
> if (rc)
> goto mem_err;
The same would apply here.
Thanks
Rob
next prev parent reply other threads:[~2014-10-16 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 16:59 [PATCH] sfc: efx: add support for skb->xmit_more Daniel Borkmann
2014-10-13 18:02 ` Edward Cree
2014-10-13 19:18 ` Daniel Borkmann
2014-10-14 18:41 ` [PATCH RFC net-next] sfc: " Edward Cree
2014-10-14 21:15 ` David Miller
2014-10-15 11:05 ` Edward Cree
2014-10-15 16:20 ` David Miller
2014-10-16 15:42 ` Jonathan Cooper
2014-10-16 16:36 ` Robert Stonehouse [this message]
2014-10-17 14:32 ` [PATCH " Edward Cree
2014-10-18 3:47 ` David Miller
2014-10-22 8:58 ` Ben Hutchings
2014-10-22 12:36 ` Edward Cree
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=543FF408.3000808@solarflare.com \
--to=rstonehouse@solarflare.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=ecree@solarflare.com \
--cc=jcooper@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--cc=sshah@solarflare.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 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).