linux-kernel - Re: [PATCH 0/6] Calxeda xgmac performance fixes

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: <20121029.140632.231750343803161384.davem@davemloft.net>
Date:	Mon, 29 Oct 2012 14:06:32 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	rob.herring@...xeda.com
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	jonathan@...masters.org, eric.dumazet@...il.com,
	mark.langsdorf@...xeda.com
Subject: Re: [PATCH 0/6] Calxeda xgmac performance fixes

From: Rob Herring <rob.herring@...xeda.com>
Date: Mon, 29 Oct 2012 12:52:39 -0500

> David,
> 
> On 10/12/2012 10:15 AM, Rob Herring wrote:
>> From: Rob Herring <rob.herring@...xeda.com>
>> 
>> This is a series of performance improvements to the xgmac driver. The most
>> significant changes are the alignment fixes to avoid alignment traps on
>> received frames and using relaxed i/o accessors.
> 
> Can you please apply this series for 3.7. They are all self-contained to
> the xgmac driver and fix some performance issues including unaligned
> access traps in the IP stack. If 3.7 is not acceptable, then 3.8 is fine.
> 
> Note that only patch 5 has a v2 version.

If you look in patchwork, these patches are marked "deferred"
which means that were not appropriate for submission when you
posted them (we were in the merge window and the net-next tree
was closed).

Which means you must repost the series, and I will apply this
to net-next for 3.8

Always check patchwork, it is never necessary to ask me questions like
this, the answers are there.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/