Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp6969639ybf; Fri, 6 Mar 2020 07:57:01 -0800 (PST) X-Google-Smtp-Source: ADFU+vvFRdPzWVwyIqHPfj02NXRH5Wp//rZm6oHObYSgpj8h3ITgi0ot5rV0y4uWdzE1IcPJLhmM X-Received: by 2002:a05:6830:108d:: with SMTP id y13mr3123823oto.241.1583510221708; Fri, 06 Mar 2020 07:57:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583510221; cv=none; d=google.com; s=arc-20160816; b=CD8+sxQMJWDBLJth4yR1FG0GE1xQJwAdc3WjgdH6vwPUzmM1/3tOHTnGNx4bwpk9UQ bOiZYgQHuhMLXQpdXQhtjquW0PCEZ9sEi5pElQkvUeaVUVUdc+wrj/U8nnpF/ViZJHJa 1PrjNo0hMOo/jpW5i0SpYYEnth8PXJOk2rd03vLQ6sRUiFf5offqPksRcj05+8KlCeKv jtE06DHVb6CjQKacjwUmh3mfvmTpm6zDJ98da7d+bXJRlLCKbU+dQt0/Q3fcT0KZaONz Vp4aouVVDzNWlcQ3OTDO9n4+4bAHlZPZ4Vc+RIMG85q8NVs/ms4hAxSrMG3NsHzv6xwe Gz8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:to:from:subject:dkim-signature; bh=ezCPULtseWvdBonQ6V0xPRaeP4ZB/PxE/0zq2zKcecE=; b=Uf3J8C5KvY1jDxZ63350gcj7R134qqe4EDcyzbMLHfsdDKVLZYwCc87rwQhTdBtScE APQaj2n/YOWs2HoRyYZ747n+X5mUZuvlccvIO9yiPZ9jTEKo51bp9+y4f4acedD1fGoU tOY1m2GtY5O3XG3KiccUMFpEHe5F6EgwwCnSUaraOu1ZJFkP0srMD1GGilsZc3ozH8H4 7F1UsAaZVzxrNaEo2Ee0CIBkxrgkjHjcX3KSdpd7MxHzC6Femw98IhuRivPGn9t+PKby 9UHtAWEXOXsuJg3T7acXUrQS/0cMXCgOr/Wqfrd6hV+S/WlW8R4way0rhMm0tnnHJXNM cq4Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@toxicpanda-com.20150623.gappssmtp.com header.s=20150623 header.b=vrJLB0AM; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m25si1584816oie.207.2020.03.06.07.56.51; Fri, 06 Mar 2020 07:57:01 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@toxicpanda-com.20150623.gappssmtp.com header.s=20150623 header.b=vrJLB0AM; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726798AbgCFP4D (ORCPT + 99 others); Fri, 6 Mar 2020 10:56:03 -0500 Received: from mail-qt1-f175.google.com ([209.85.160.175]:44610 "EHLO mail-qt1-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726733AbgCFP4C (ORCPT ); Fri, 6 Mar 2020 10:56:02 -0500 Received: by mail-qt1-f175.google.com with SMTP id h16so2013471qtr.11 for ; Fri, 06 Mar 2020 07:56:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toxicpanda-com.20150623.gappssmtp.com; s=20150623; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=ezCPULtseWvdBonQ6V0xPRaeP4ZB/PxE/0zq2zKcecE=; b=vrJLB0AMnGlO//iPUaQj4czq/Ymit0XSXn1kNCy8dDIfN4SAIn0VAB/1G2P2aIDpAU Q27jZMqu4vigDxjEMZyxINWUtIYfkl6/mAt+DeCjj4wMTZs2RV/kEGdrj66XgR5U7ES2 wMm/c7XuXN1jlz66+O3Hn8wnQULPar1idqw7jtMSp27Zoz1C708TI1chwf9e+jI/GDFQ vCbYi/CLGURNzDWhNREp1p+ANBwZhR29YBXFznGQq+ABEJUoUKb6c/lAAuCEMTH/AYd1 dHzKsl398YVeJCoLhooB/CBNL6dXtcStxFOrJ5HA0DD1cJht5EBgTz5+RJ/FijRjxZbf TJFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ezCPULtseWvdBonQ6V0xPRaeP4ZB/PxE/0zq2zKcecE=; b=C1Nj1PicSeQALU+gzC7qtQGINp9XcLGkeM9YOzLFuZonvG15APLcwtkoWrLO+7FZXU Ncq2KwhDoKl+hm9KafcXaTIFWv/DArNFviIyHQDRdqmeLpndaCnQ7wpM1bU9QnFGrE9m 4h2W6TK+jhtQGQhx+Inypg2qVLNFCXFW17JThExHqE5IbXjiLTeTDaOUHCY64+F/Mnos Wxx5yGB1PNLcotJgb4B0maSC6/ChCYfZUtquAGyUz37zEO1V8ufu7kNZtk/WHiulq7S/ GoqXZiDAXfzJNv+/MKN0fz0colW7Uz+aRjkAXXKJDq+xPziS9c2GqmQFYV5AEhoPfdWs Tqkw== X-Gm-Message-State: ANhLgQ2DfX/9Ngkfx8ayk9O/oFe665iy44vv/PD6pj2+2h/kUNHi78x0 LGdEbi+Z5M1NSSgbdTTy57HAjA== X-Received: by 2002:aed:2823:: with SMTP id r32mr3419004qtd.320.1583510159759; Fri, 06 Mar 2020 07:55:59 -0800 (PST) Received: from [192.168.1.106] ([107.15.81.208]) by smtp.gmail.com with ESMTPSA id 4sm9421817qkl.79.2020.03.06.07.55.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 06 Mar 2020 07:55:58 -0800 (PST) Subject: Re: [LSFMMBPF TOPIC] Killing LSFMMBPF From: Josef Bacik To: lsf-pc , Linux FS Devel , linux-mm@kvack.org, linux-xfs@vger.kernel.org, Btrfs BTRFS , bpf@vger.kernel.org, linux-ext4@vger.kernel.org, linux-block@vger.kernel.org References: Message-ID: <94dff81a-f0bb-1f91-999b-50bf29b75f4a@toxicpanda.com> Date: Fri, 6 Mar 2020 10:55:57 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On 3/6/20 9:35 AM, Josef Bacik wrote: > Hello, > > This has been a topic that I've been thinking about a lot recently, mostly > because of the giant amount of work that has been organizing LSFMMBPF.  I was > going to wait until afterwards to bring it up, hoping that maybe it was just me > being done with the whole process and that time would give me a different > perspective, but recent discussions has made it clear I'm not the only one. > > LSFMMBPF is not useful to me personally, and not an optimal use of the > communities time.  The things that we want to get out of LSFMMBPF are (generally) It has been pointed out to me that this appears to make it sound like I think the whole conference is useless. I would like to make it clear that this is not the case at all. This is still the only conference that I make sure to make it to every year, because all of the reasons I list. The point of me posting this is to get us to put some real thought into what would be the most optimal way to accomplish the same things in a different way. Maybe I should have titled it "Make LSFMMBPF great again!" instead. I feel that there is a lot of fat to trim here, and many voices not being heard because of the way the conference is organized. If I'm the only one then that's cool, but if I'm not I'd like people to think really hard about what the ideal meetup looks like, and how we can move in that direction. Thanks, Josef