netdev - Re: [PATCH 1/2] rps: core implementation

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 20 Nov 2009 09:08:10 -0800
From:	Tom Herbert <therbert@...gle.com>
To:	Jarek Poplawski <jarkao2@...il.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] rps: core implementation

> The description reads: "This solution queues packets early on in the
> receive path on the backlog queues of other CPUs.", so I'm not sure
> it's intended.

That is precisely the intent.  Getting packets quickly distributed to
the target cpus maximizes parallelism and reduces latency.

Did you test it like this (and it was visibly worse)?:
>
>        if (cpu < 0 || cpu == smp_processor_id())
>
>> +             return __netif_receive_skb(skb);
>> +     else
>> +             return enqueue_to_backlog(skb, cpu);
>> +}
>> +
This increases overall latency due to head of line blocking which will
outweigh the benefits of optimizing for this one case.

Tom
--
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