netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Miller <davem@davemloft.net>
Cc: ming.lei@canonical.com, oneukum@suse.de,
	sarah.a.sharp@linux.intel.com, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH v4 0/4] USB & USBNET: loose SG check and support usbnet DMA SG
Date: Fri, 9 Aug 2013 14:13:23 -0700	[thread overview]
Message-ID: <20130809211323.GA20120@kroah.com> (raw)
In-Reply-To: <20130809.141217.555889385998745188.davem@davemloft.net>

On Fri, Aug 09, 2013 at 02:12:17PM -0700, David Miller wrote:
> From: Ming Lei <ming.lei@canonical.com>
> Date: Thu,  8 Aug 2013 21:48:21 +0800
> 
> > This patchset allows drivers to pass sg buffers which size can't be divided
> > by max packet size of endpoint if the host controllers(such ax xHCI) support
> > this kind of sg buffers.
> > 
> > Previously we added check[1] on the situation and don't allow these sg buffers
> > passed to USB HCD, looks the check is too strict to make use of new feature of
> > new hardware(xHCI) for some applications(such as network stack) which can't
> > provide this kind of sg buffers to usbnet driver, so the patch looses the check
> > in case that the host controller supports it.
> > 
> > Patch 3/4 implements DMA SG on usbnet driver, and patch 4/4 uses it on ax88179_178a
> > USB3 NIC for supporting TSO, so both CPU utilization and tx throughput can be
> > improved with TSO and DMA SG in case of the USB NIC is attached to xHCI controller.
> > 
> > This patchset depends on both net-next and usb-next tree, so hope David and Greg
> > to figure out one elegent way to merge it.
> 
> Greg feel free to merge this in via your USB tree with my:
> 
> Acked-by: David S. Miller <davem@davemloft.net>

Thanks, will do.

greg k-h

      reply	other threads:[~2013-08-09 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 13:48 [PATCH v4 0/4] USB & USBNET: loose SG check and support usbnet DMA SG Ming Lei
2013-08-08 13:48 ` [PATCH v4 1/4] USB: introduce usb_device_no_sg_constraint() helper Ming Lei
2013-08-08 16:28   ` Eric Dumazet
2013-08-08 13:48 ` [PATCH v4 2/4] USB: XHCI: mark no_sg_constraint Ming Lei
     [not found]   ` <1375969705-24877-3-git-send-email-ming.lei-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-08-08 16:28     ` Eric Dumazet
2013-08-08 13:48 ` [PATCH v4 3/4] USBNET: support DMA SG Ming Lei
     [not found]   ` <1375969705-24877-4-git-send-email-ming.lei-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-08-08 16:27     ` Eric Dumazet
2013-08-08 13:48 ` [PATCH v4 4/4] USBNET: ax88179_178a: enable tso if usb host supports sg dma Ming Lei
     [not found]   ` <1375969705-24877-5-git-send-email-ming.lei-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-08-08 16:01     ` Eric Dumazet
     [not found] ` <1375969705-24877-1-git-send-email-ming.lei-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-08-09 21:12   ` [PATCH v4 0/4] USB & USBNET: loose SG check and support usbnet DMA SG David Miller
2013-08-09 21:13     ` Greg KH [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=20130809211323.GA20120@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-usb@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=sarah.a.sharp@linux.intel.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).