netdev - Re: [PATCH v2 net-next] documentation: Document issues with VMs and XPS and drivers enabling it on their own

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] [day] [month] [year] [list]

Message-ID: <CALx6S34Qak8vbMakLCTpf5UTNsZQ0rpLWNjHMxUnF3sULFQMOw@mail.gmail.com>
Date:   Mon, 29 Aug 2016 10:35:50 -0700
From:   Tom Herbert <tom@...bertland.com>
To:     Rick Jones <rick.jones2@....com>
Cc:     David Miller <davem@...emloft.net>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>,
        Alexander Duyck <alexander.duyck@...il.com>
Subject: Re: [PATCH v2 net-next] documentation: Document issues with VMs and
 XPS and drivers enabling it on their own

On Mon, Aug 29, 2016 at 9:26 AM, Rick Jones <rick.jones2@....com> wrote:
> On 08/27/2016 12:41 PM, Tom Herbert wrote:
>>
>> On Fri, Aug 26, 2016 at 9:35 PM, David Miller <davem@...emloft.net> wrote:
>>>
>>> From: Tom Herbert <tom@...bertland.com>
>>> Date: Thu, 25 Aug 2016 16:43:35 -0700
>>>
>>>> This seems like it will only confuse users even more. You've clearly
>>>> identified an issue, let's figure out how to fix it.
>>>
>>>
>>> I kinda feel the same way about this situation.
>>
>>
>> I'm working on XFS (as the transmit analogue to RFS). We'll track
>> flows enough so that we should know when it's safe to move them.
>
>
> Is the XFS you are working on going to subsume XPS or will the two continue
> to exist in parallel a la RPS and RFS?
>
XPS selects the queue, XFS prevents changing the queues when OOO could
occur. I am thinking that XFS is only applicable when we don't have a
socket tracking OOO. Idea is to have a flow table indexed by packet
hash that gives the current TX queue for match flows. The TX queue
comes from doing XPS. We only change the queue used by flows if that
won't result in OOO as determined by tracking the queue similar to how
we do RFS.

Tom

> rick jones
>