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]
Message-ID: <53B2C3E8.7030903@mentor.com>
Date:	Tue, 1 Jul 2014 09:21:28 -0500
From:	Nathan Lynch <Nathan_Lynch@...tor.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	<linux-arm-kernel@...ts.infradead.org>, <netdev@...r.kernel.org>,
	Fugang Duan <B38611@...escale.com>
Subject: Re: [PATCH CFT 00/30] Initial round of Freescale FEC ethernet patches

[apologies if this is a duplicate, I got a weird SMTP error from my
organization's mail server when I tried to send this yesterday]

On 06/27/2014 10:15 AM, Russell King - ARM Linux wrote:
> This is v2 of my initial round of patches (roughly half of my total
> patch set) for the Freescale FEC driver.
> 
> I'm sending this set out for comments and testing.  So far, I have
> had only one ack for one patch in this series, this is pretty poor,
> so I'm now sending it with a CFT tag instead.

FWIW I've given your fec-testing branch some testing on BD-SL-i.MX6
(Sabre Lite) with 3.16-rc2 (-rc1 has some issue with detecting the mmc).
 Mainly running glibc 'make check' with SSH, NFSv4, IPv4 on a gigabit
switch.  This workload wasn't exhibiting problems before your patches
and it does not appear to be regressed by them.

I wanted to test it because I've noticed hard-to-characterize sluggish
interactive response in SSH sessions on this system.  Like key echo
takes 0.2 seconds too long... sometimes.  I guess it could be anything,
but I haven't encountered it yet with your patches.

--
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