netdev - Re: [RFC PATCH] net, rps: bypass enqueue_to

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: <1387374979.19078.309.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Wed, 18 Dec 2013 05:56:19 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Zhi Yong Wu <zwu.kernel@...il.com>
Cc:	therbert@...gle.com, netdev@...r.kernel.org,
	Zhi Yong Wu <wuzhy@...ux.vnet.ibm.com>
Subject: Re: [RFC PATCH] net, rps: bypass enqueue_to_backlog()

On Wed, 2013-12-18 at 21:03 +0800, Zhi Yong Wu wrote:
> From: Zhi Yong Wu <wuzhy@...ux.vnet.ibm.com>
> 
> When local cpu is just target cpu which will handle network soft irq,
> the packet should be directly injected to network stack, by bypassing
> enqueue_to_backlog(), it can speed up the packet processing.
> 
> HI, guys
> 
> I checked the first several versions of RPS patch which seemed to have
> this condition determination, but why was it removed later? Do i miss
> anything? if yes, please correct me, thanks.
> 
> Signed-off-by: Zhi Yong Wu <wuzhy@...ux.vnet.ibm.com>
> ---

Hmm... Could you elaborate ?

At which point do you think this condition was tested or removed ?

I think the idea was to drain NIC RX queues as fast as possible, then :

- Send the IPI to remote cpus
- process our queue in parallel with other cpus processing their own
queue.

If we process our packets through whole stack, packets for other cpus
will have a fair amount of extra latency.

Thats a tradeoff I suppose.


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