Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bjorn@mork.no
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	oneukum@suse.de, gsuarez@smithmicro.com,
	alexey.orishko@stericsson.com, y.kaliuta@gmail.com
Subject: Re: [PATCH net] net: cdc_mbim: send ZLP only for the specific buggy device
Date: Wed, 23 Jan 2013 13:47:26 -0500 (EST)	[thread overview]
Message-ID: <20130123.134726.112187775032509711.davem@davemloft.net> (raw)
In-Reply-To: <1358938622-18344-1-git-send-email-bjorn@mork.no>

From: Bjørn Mork <bjorn@mork.no>
Date: Wed, 23 Jan 2013 11:57:02 +0100

> Reverting 328d7b8 and instead adding an exception for the
> Sierra Wireless MC7710.
> 
> commit 328d7b8 (net: cdc_mbim: send ZLP after max sized NTBs)
> added a workaround for an issue observed on one specific device.
> Concerns were raised that this workaround adds a performance
> penalty to all devices based on questionable, if not buggy,
> behaviour of a single device:
> 
>  "If you add ZLP for NTBs of dwNtbOutMaxSize, you are heavily affecting CPU
>   load, increasing interrupt load by factor of 2 in high load traffic
>   scenario and possibly decreasing throughput for all other devices
>   which behaves correctly."
> 
>  "The idea of NCM was to avoid extra ZLPs. If your transfer is exactly
>   dwNtbOutMaxSize, it's known, you can submit such request on the receiver
>   side and you do not need any EOT indicatation, so the frametime can be
>   used for useful data."
> 
> Adding a device specific exception to prevent the workaround from
> affecting well behaved devices.
> 
> The assumption here is that needing a ZLP is truly an *exception*.
> We do not yet have enough data to verify this.  The generic
> workaround in commit 328d7b8 should be considered acceptable despite
> the performance penalty if the exception list becomes a maintainance
> hassle.
> 
> Cc: Alexey ORISHKO <alexey.orishko@stericsson.com>
> Cc: Yauheni Kaliuta <y.kaliuta@gmail.com>
> Signed-off-by: Bjørn Mork <bjorn@mork.no>

Applied.

      reply	other threads:[~2013-01-23 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 10:57 [PATCH net] net: cdc_mbim: send ZLP only for the specific buggy device Bjørn Mork
2013-01-23 18:47 ` David Miller [this message]

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=20130123.134726.112187775032509711.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexey.orishko@stericsson.com \
    --cc=bjorn@mork.no \
    --cc=gsuarez@smithmicro.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=y.kaliuta@gmail.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