From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Adam Wallis <awallis@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.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: Mon, 21 May 2018 16:53:17 +0300 [thread overview]
Message-ID: <9bd5c1a7-3741-775e-bc87-2fd6d89a63dd@linux.intel.com> (raw)
On 21.05.2018 15:56, Adam Wallis wrote:
> On 5/16/2018 2:02 AM, Greg Kroah-Hartman wrote:
>> On Tue, May 15, 2018 at 04:51:53PM -0400, Adam Wallis wrote:
>>
>> Ok, fair enough, I was hoping that "modern" systems would have better
>> NUMA memory interconnects. I guess that isn't the case still :(
>
> Things will keep improving, I'm sure.
>
> Mathias, did you have anything you need reworked with this patch or any specific
> comments on the overall patch?
>
If there's a performance benefit in adding these then I'm all for it.
for ring related allocations it makes sense.
Not sure if if there's any benefit in allocating the scratchpad structures from
a closer node, or any harm? xhci driver doesn't really access scratchpad that frequently.
The port related structures are changing completely, so xhci->usb2_ports xhci->usb3_ports
and other related are going away. Just sent a series for that. So some rebasing is needed.
-Mathias
---
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
next reply other threads:[~2018-05-21 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 13:53 Mathias Nyman [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 12:56 Adam Wallis
2018-05-16 6:02 Greg Kroah-Hartman
2018-05-15 20:51 Adam Wallis
2018-05-15 15:07 Greg Kroah-Hartman
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=9bd5c1a7-3741-775e-bc87-2fd6d89a63dd@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=awallis@codeaurora.org \
--cc=gregkh@linuxfoundation.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.