All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Adam Wallis <awallis@codeaurora.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	linux-usb@vger.kernel.org, timur@codeaurora.org
Subject: usb: xhci: force all memory allocations to node
Date: Tue, 15 May 2018 17:07:37 +0200	[thread overview]
Message-ID: <20180515150737.GA23227@kroah.com> (raw)

On Tue, May 15, 2018 at 09:53:57AM -0400, Adam Wallis wrote:
> The xhci driver forces DMA memory to be node aware, however, there are
> several ring-related memory allocations that are not memory node aware.
> This patch resolves those *alloc functions to be allocated on the proper
> memory node.

Does this really do anything?  Given the speed of USB3 at the moment,
does fixing the memory to the node the PCI device is on show any
measurable speedups?  Last I remember about NUMA systems, it wasn't
always a win depending on where the irq came in from, right?

thanks,

greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-05-15 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 15:07 Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-22  7:35 usb: xhci: force all memory allocations to node Mathias Nyman
2018-05-21 16:42 Adam Wallis
2018-05-21 13:53 Mathias Nyman
2018-05-21 12:56 Adam Wallis
2018-05-16  6:02 Greg Kroah-Hartman
2018-05-15 20:51 Adam Wallis
2018-05-15 13:53 Adam Wallis

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=20180515150737.GA23227@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=awallis@codeaurora.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=timur@codeaurora.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.