linux-kernel - Re: Cache Allocation Technology Design

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

Message-ID: <20141030171247.GC378@htj.dyndns.org>
Date:	Thu, 30 Oct 2014 13:12:47 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Tim Hockin <thockin@...kin.org>
Cc:	linux-kernel@...r.kernel.org, "Auld, Will" <will.auld@...el.com>,
	Matt Fleming <matt@...sole-pimps.org>,
	Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"Fleming, Matt" <matt.fleming@...el.com>,
	Vikas Shivappa <vikas.shivappa@...el.com>
Subject: Re: Cache Allocation Technology Design

On Thu, Oct 30, 2014 at 07:58:34AM -0700, Tim Hockin wrote:
> Another reason unified hierarchy is a bad model.

Things wrong with this message.

1. Top posted.  It isn't clear which part you're referring to and this
   was pointed out to you multiple times in the past.

2. No real thoughts or technical details.  Maybe you had some in your
   head but nothing was elaborated.  This forces me to guess what you
   had on mind when you produced the above sentence and of course me
   not being you this takes a considerable amount of brain cycle and
   I'd still end up with multiple alternative scenarios that I'll have
   to cover.

3. Needlessly loaded expression, which forces me to respond.

Combined, this is just rude and you've been showing this type of
behavior multiple times.  Behave yourself.

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