linux-kernel - Re: [RFCv2 00/10] xhci: re-work command queue management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPcyv4ipHdM7HnB=P+eWrPc9kBRzPoxOw+Of6eS+QkcYzk2vfA@mail.gmail.com>
Date:	Wed, 5 Feb 2014 09:27:55 -0800
From:	Dan Williams <dan.j.williams@...el.com>
To:	David Laight <David.Laight@...lab.com>
Cc:	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"sarah.a.sharp@...ux.intel.com" <sarah.a.sharp@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFCv2 00/10] xhci: re-work command queue management

On Wed, Feb 5, 2014 at 9:05 AM, David Laight <David.Laight@...lab.com> wrote:
> From: Dan Williams
>> Yes, but I think we need to centralize the context under which
>> commands are submitted.  The complicating factor is the mix of
>> synchronous command submission and interrupt driven asynchronous
>> command queuing.  I think we can simplify it by making it all
>> submitted from a single event queue context.  I'm investigating if
>> that is a workable solution...
>
> Given that the entire network stack runs from (I believe) 'process level'
> contexts (NAPI functions),

Not really.  Much of the network stack runs under softirq context.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/