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] [day] [month] [year] [list]
Message-Id: <20141025.162122.1889567772198459311.davem@davemloft.net>
Date:	Sat, 25 Oct 2014 16:21:22 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	sowmini.varadhan@...cle.com
Cc:	bob.picco@...cle.com, dwight.engen@...cle.com,
	raghuram.kothakota@...cle.com, netdev@...r.kernel.org
Subject: Re: [PATCHv6 net-next 0/3] sunvnet: NAPIfy sunvnet

From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Date: Sat, 25 Oct 2014 15:11:52 -0400

> This patchset converts the sunvnet driver to use the NAPI framework.
> Changes since v4 to Patch1: 
>   vnet_event accumulates LDC_EVENT_* bits into rx_event. 
>   vnet_event_napi() unrolls send_events() logic to process all rx_event bits.
> Changes since v5: 
>   Patch 1: use net_device.h definition for NAPI_POLL_WEIGHT.
>   Drop sparclinux changes (patch3) per David Miller feedback 
> 
> Patch 1 in the series addresses the packet-receive path- all
> the vnet_event() processing is moved into NAPI context.
> This patch is dependant on the sparc-next commit:
>   "sparc64: Add vio_set_intr() to enable/disable Rx interrupts"
>   (sparc commit id ca605b7dd740c8909408d67911d8ddd272c2b320)
> 
> Patch 2 uses RCU to fix race conditions between vnet_port_remove and
> paths that access/modify port-related state, such as vnet_start_xmit.
> 
> Patch 3 leverages from the NAPIfied Rx path, 
> dropping superfluous usage of the irqsave/irqrestores on the vio.lock
> where possible.

Series 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