netdev - Re: Pull request: sfc-next 2013-06-24

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Jun 2013 16:12:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	netdev@...r.kernel.org, linux-net-drivers@...arflare.com
Subject: Re: Pull request: sfc-next 2013-06-24

From: Ben Hutchings <bhutchings@...arflare.com>
Date: Mon, 24 Jun 2013 21:11:48 +0100

> The following changes since commit 37173488400704f1a05656616cd12baa9e03173b:
> 
>   bnx2x: Fix compilation with no IOV support (2013-06-24 01:47:47 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next.git for-davem
> 
> for you to fetch changes up to 636d73da27e83ce4882f8823f79063bb37980961:
> 
>   sfc: Improve test for IOMMU in use (2013-06-24 20:02:53 +0100)
> 
> 1. Make EEH recovery work when using legacy interrupts, from Alexandre
>    Rames.
> 
> 2. Enable accelerated RFS for VLAN-tagged flows, from Andy Lutomirski.
> 
> 3. Improve performance for non-TCP (and particularly UDP) traffic, which
>    regressed in 3.10 when we switched to always allocating paged RX
>    buffers.  Partly by Jon Cooper.
> 
> 4. Some minor bug fixes to IOMMU detection, timestamping capabilities,
>    and IRQ cleanup on the probe failure path.
> 
> I've dropped the RX skb cache, which improved some benchmarks but
> perhaps needs some reworking to be more generally useful.

Pulled, thanks Ben.
--
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