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] [day] [month] [year] [list]
Date:	Thu, 25 Jun 2015 05:23:27 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	_govind@....com
Cc:	netdev@...r.kernel.org, ssujith@...co.com, benve@...co.com
Subject: Re: [PATCH net-next v2] enic: use atomic_t instead of spin_lock in
 busy poll

From: Govindarajulu Varadarajan <_govind@....com>
Date: Thu, 25 Jun 2015 16:02:04 +0530

> We use spinlock to access a single flag. We can avoid spin_locks by using
> atomic variable and atomic_cmpxchg(). Use atomic_cmpxchg to set the flag
> for idle to poll. And a simple atomic_set to unlock (set idle from poll).
> 
> In napi poll, if gro is enabled, we call napi_gro_receive() to deliver the
> packets. Before we call napi_complete(), i.e while re-polling, if low
> latency busy poll is called, we use netif_receive_skb() to deliver the packets.
> At this point if there are some skb's held in GRO, busy poll could deliver the
> packets out of order. So we call napi_gro_flush() to flush skbs before we
> move the napi poll to idle.
> 
> Signed-off-by: Govindarajulu Varadarajan <_govind@....com>

Applied, thanks.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ