linux-kernel - Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional

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

Message-Id: <20170603035915.GA23375@linux.vnet.ibm.com>
Date:   Fri, 2 Jun 2017 20:59:15 -0700
From:   "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:     Nicolas Pitre <nicolas.pitre@...aro.org>
Cc:     linux-kernel@...r.kernel.org, josh@...htriplett.org
Subject: Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional

On Fri, May 12, 2017 at 12:10:05PM -0700, Paul E. McKenney wrote:
> On Fri, May 12, 2017 at 02:59:48PM -0400, Nicolas Pitre wrote:
> > On Fri, 12 May 2017, Paul E. McKenney wrote:

[ . . . ]

> > No.  "Available in mainline" is the name of the game for all I do. If it 
> > can't be made acceptable for mainline then it basically has no chance of 
> > gaining traction and becoming generally useful. My approach is therefore 
> > to always find solutions that can be maintained upstream and contributed 
> > to with minimal fuss by anyone.
> 
> OK, then wish me luck.  ;-)

And still quite a bit of back and forth.  How are things with tty?

One question that came up -- what sort of SoCs are you targeting?
A number of people are insisting that smartphone SoCs with 256M DRAM
are the minimal systems of the future.  This seems unlikely to me,
given the potential for extremely cheap SoCs with EDRAM or some such,
but figured I should ask what you are targeting.

							Thanx, Paul