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
| ||
|
Message-ID: <412e6f7f0911140530h1fac3053v5d5fe30ceac303a1@mail.gmail.com> Date: Sat, 14 Nov 2009 21:30:52 +0800 From: Changli Gao <xiaosuo@...il.com> To: Eric Dumazet <eric.dumazet@...il.com> Cc: Stephen Hemminger <shemminger@...tta.com>, Jarek Poplawski <jarkao2@...il.com>, "David S. Miller" <davem@...emloft.net>, Patrick McHardy <kaber@...sh.net>, Tom Herbert <therbert@...gle.com>, netdev@...r.kernel.org Subject: Re: [PATCH] ifb: add multi-queue support On Sat, Nov 14, 2009 at 8:53 PM, Eric Dumazet <eric.dumazet@...il.com> wrote: > Changli Gao a écrit : >> Yea, the overhead of SoftIRQ is less than kernel threads, and I'll try >> to find a way to solve both flexibility and efficiency. Maybe I need >> some real NIC drivers as examples. Is there a standard API to bind RQs >> of NIC to CPUs, such as ioctl or setsockopt? > > Thats a good question... napi is bound to a cpu, and you'll need > things that were done by Tom Herbert in its RPS patch, to > be able to deleguate work to remote cpus napi contexts. > > But if we consider RPS being close to be committed, shouldnt > IFB use its, in order to not duplicate changes ? > > Or, if you prefer, once RPS is in, we dont need to change IFB, since > RPS will already split the load to multiple cpus before entering IFB. > > I had known RPS before I began my IFB work, so I added Tom to the CC list, but I don't know if RPS will be in the mainline. Since there isn't any core change in IFB as is in RPS, I think it is easier to merge IFB into the mainline. If RPS is merged before IFB-MQ, I'll give IFB-MQ up, and vice versa I think. -- Regards, Changli Gao(xiaosuo@...il.com) -- 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
Powered by blists - more mailing lists