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: <20141106.162516.1083429539800319166.davem@davemloft.net> Date: Thu, 06 Nov 2014 16:25:16 -0500 (EST) From: David Miller <davem@...emloft.net> To: eric.dumazet@...il.com Cc: netdev@...r.kernel.org, ogerlitz@...lanox.com, willemb@...gle.com Subject: Re: [PATCH net-next] net: gro: add a per device gro flush timer From: Eric Dumazet <eric.dumazet@...il.com> Date: Wed, 05 Nov 2014 16:55:20 -0800 > @@ -4430,8 +4432,19 @@ void napi_complete(struct napi_struct *n) > if (unlikely(test_bit(NAPI_STATE_NPSVC, &n->state))) > return; > > - napi_gro_flush(n, false); > + if (n->gro_list) { > + unsigned long timeout = 0; > + > + if (n->napi_rx_count) > + timeout = n->dev->gro_flush_timeout; Under what circumstances would we see n->gro_list non-NULL yet n->napi_rx_count == 0? I'm not so sure it can happen. Said another way, it looks to me like you could implement this using less state. -- 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