From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua0-f182.google.com (mail-ua0-f182.google.com [209.85.217.182]) by dpdk.org (Postfix) with ESMTP id 2F43D2BA1 for ; Fri, 11 Aug 2017 23:18:30 +0200 (CEST) Received: by mail-ua0-f182.google.com with SMTP id w45so19767593uac.5 for ; Fri, 11 Aug 2017 14:18:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infinite-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fkMlpZzvgpwXzdfrOjrU/kWEK/LLvJGnmhCrWQ+eirQ=; b=o2wwXI96qGtRrhbh0M0xt5xQwh629TZn4/qnZEU5UZbEoRwPot0hsgYCbp7Ko++5j1 f9/wSHMsRZyuXb1P/o6C7EUy/wgqPAjIEpfSOs3u+X6/FzXRKl1KusgkPRklfy1A6Y3z xsqbAnaX5m04geOf+JL/Et6M8YOd/jUP8L+wwgd8X/YfXZt4Wvme2xj74/2fUOIoioSS UIuOeoGjBFQc/F/vM70jomY6zOpsf0SaERJ0kV/UxoVF5DTcK9YhFJlBUnkYTUBbsN9Y TycY/B07lAZNE6vz8qajvxRfR6I46Wu4mnnC25dUFdvDFIXGeTGSsYrb5bfhqGJfyt92 CUVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fkMlpZzvgpwXzdfrOjrU/kWEK/LLvJGnmhCrWQ+eirQ=; b=lxl7FVs0Xi9DOvSVtze3ag2RFT7uUnSWO6QonHOJsSmBDARTRtHekkualJUqQ6XxDI hyoe+4Gp0brQ/uQsAnlNSVz3UraXyJEvnHikeGQPa8Hy7CRV/cpV2m7tT6nLwwSIWL22 dTukfURZel0lmNlZz+9obmcpEWZTSq0VO1P2mGMd8Xqem1Qe/7FcTAy6Ep4t1eD/OmI+ oOOBpFd93jqceQlyqMlI+4XDTN9YUR+kK5L1u8QsO+vLdCrNyTM6GkDWN5tkEvv1t91h JaSM8UNKTP9VA3FBfiWdBh+Cwd7BAqZut0JhqE+tvKJLSEKOtjXQlUV172EbMXeyRyvC GxJg== X-Gm-Message-State: AHYfb5hettvhE+kLxVYaFcQD/8Uhv+DjzpHhpaE5fOCEv+TLZwStNxs9 a/u2l1g//mY+rioZfg8W5l5NBXqH11bw X-Received: by 10.176.24.97 with SMTP id j33mr10520271uag.125.1502486309567; Fri, 11 Aug 2017 14:18:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.143.87 with HTTP; Fri, 11 Aug 2017 14:18:29 -0700 (PDT) In-Reply-To: <20170811202923.GA71096@bricha3-MOBL3.ger.corp.intel.com> References: <20170809202132.GA13981@hmswarspite.think-freely.org> <20170811202923.GA71096@bricha3-MOBL3.ger.corp.intel.com> From: Jay Rolette Date: Fri, 11 Aug 2017 16:18:29 -0500 Message-ID: To: Bruce Richardson Cc: Neil Horman , DPDK Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Announcement of SSE requirement change in dpdk X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 21:18:30 -0000 On Fri, Aug 11, 2017 at 3:29 PM, Bruce Richardson < bruce.richardson@intel.com> wrote: > On Wed, Aug 09, 2017 at 04:21:32PM -0400, Neil Horman wrote: > > Can anyone point out to me when and where the change to require SSE4.2 > was > > dicussed? The first I saw of it was when the commit to the release > notes went > > in on August 3, and I can find no prior mention of it, save for the > patches that > > went in separately in the prior weeks. > > > > Neil > > > There was no real widespread discussion of it, if that's what you are > looking for. I made the proposal via patch, and it was reviewed and > acked by a number of folks, with nobody raising any objections at the > time. Possibly it was a change that should have been more widely > publicised ahead of time, but I'm not sure what form that publicization > should have taken, since all tech discussion happens on the dev mailing > list anyway. > Not that I'm planning any similar changes, but for the future, what do > you think the process for changes like this should be - and what changes > would classify for it? If we have a process problem, let's try and fix > it. > > Regards, > /Bruce. > I'd suggest removing support for any hardware (CPUs or NICs) should require a much "louder" announcement. This particular one didn't hit my company, but when you have hardware out in the field that you are expected to provide on-going software updates for, these sort of changes are painful. The LTS tree helps considerably with this, but definitely deserves more publicity than usual. $0.02 Jay