From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pf1-f174.google.com (mail-pf1-f174.google.com [209.85.210.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9E3AA325714 for ; Fri, 24 Apr 2026 04:28:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777004919; cv=none; b=i7f1HAGR3JCIwZTlFD8mG4hhfkCkvc1XKaYG4bu66DgOj0HoDyEZcQUf8ggD0mjROTc6Ly873K/dJnaFuIBu70UhyG1npGNqvHGPI5upGRyfWKKrvMp7l1z6B9e5gZSjN+dstu79/NnsoQVBFeWw14fU2TMJFGxyapL393gSQ3A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777004919; c=relaxed/simple; bh=deWB6UrI5bI99n3jNuoT5xgmAqlYj70Qfhs0/y0QX9M=; h=From:To:Cc:Subject:In-Reply-To:Date:Message-ID:References; b=nwjmCmngd0e9dwtQM8yIAvSsG+REFRIl6RwqdM8TAAZPMbGEnFsRjIt3v7v6miU/gtR9rkR9KIXytLK0c2CGhSiWNGAmCptLdbe/bR3c+wJzvDPwfHMCzlwrJPsGMj75N9WdQlu3NCQAa3bWCKjGjiEly7YTuA2C/clP8KzY28k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=cWIiTl8J; arc=none smtp.client-ip=209.85.210.174 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="cWIiTl8J" Received: by mail-pf1-f174.google.com with SMTP id d2e1a72fcca58-82cf636dac8so3164006b3a.3 for ; Thu, 23 Apr 2026 21:28:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1777004917; x=1777609717; darn=vger.kernel.org; h=references:message-id:date:in-reply-to:subject:cc:to:from:from:to :cc:subject:date:message-id:reply-to; bh=xij6ep2gWC7gef2Qky7OxxlHC1yt3hwCxCR56tcvUXc=; b=cWIiTl8JHWvMEvypf/0To1/2JH1aepp8+jvD7bdYs37I9x7pjWckXi4ihZI+pyXN3H arPNZVCvss0VVyu4ZHm5Mi3evPgMJ+S64SmpM908LkmJMaqCxPLSQ3CY9hDjJkRiILzP EQhwnoqeYiR6XNhaCtWAeH8wtjkA5PRBQ7/wJdhYHorsc1vmZCc60pmxVF4y8QcmOrO8 K2cAn7j3JSbJgg6tnbi1lW5jbtsvDyYoinSR0th52s284jlZ1KQyOCOKLl8tM8wNvA/I 2sdmdqMVHDinwCV/FLBAff4/wzOfZllCZKCJyF4ETq05VGWe14oezZ8ibMjNuAnSD2Y1 dTeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777004917; x=1777609717; h=references:message-id:date:in-reply-to:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=xij6ep2gWC7gef2Qky7OxxlHC1yt3hwCxCR56tcvUXc=; b=ZoDwNw8dA4lWMoOIanMiEQVcKrbxKvSIXfDr78D1iuZc7GGgDDRKxp/nw3iBAk9Jge 8Y4FCCifxK0SYFsqS6+63tDsS4/9MLDFnThtxoT6RHUccYeL2G6p7v+OlGVbTtiY/Rjv ANSn26a6Igv524+kLqC2XV26eMycdt3ThkB6a2xFa83z4+vi/HUKZb5lyNNJMLcUh7Vj gT0aWaMVSPVs7iKHo5ruTGv50YcpCu+Jw62aPVkDrYQZtVDEsGz/xAH6TwCaak30vZSx FAzTDSubC7bZvbR/ZBoRc77elycxVpfpIjJp+4vRqYwaeThIjNSBw1M6NFpfbSu0CuAx aWgg== X-Forwarded-Encrypted: i=1; AFNElJ/ljGi0hXQilcRM03YJkJeUQ5unsJpyIdSUOULYsv6Z42e+7tK3VmKS3XwPxUq6BT/HF/uCCjP7p2cosKnx@vger.kernel.org X-Gm-Message-State: AOJu0YxgcjuAk9CycR2Q6UCbMiUxhBMvTdKORr/V3s3WJhck/xOxFuHp +vzsFsX/snoDXa+6AjMJ8B2Av/HLhyjWBhoko7jiRDZw74yNQ26OSiXBGN09AA== X-Gm-Gg: AeBDiet4+Yn7wqXhvHp7MT3yO2trKNY7zP4zNbH7kM8X3VQNYZI1Ol81FuZWWNyxr/r mNuffrNwO55B6kdl5XRIyYlw8a2EYlDq09a3DNcwueH1XRsLZ2aqkuzxzH1EGyOy/ZzBdqkKJ9w ba3jm0XZymsfRVJ/cgaW3S6dOPo883lXHfA01tfX9ks7opCRon97VfsMUxNTwSMNOi3/QLCXmcs fGcxe3cinLgoghGYP58BnU/x8BTKUDZNY/2mzM/URZFLYjLW8XyC2TdG6p6443wKs352pf0v3/b fPbGTw8UH8W44FPbGqYW9CctOgLu/YAh2B5gCmQJwgjZHbsI/XHvISIHf/S0tt0c68temHo3dzO 0niav+YyV4QL2+eHX0MHRXtTyB2fP+cSAHMQ7+Xgz/6X/4OwCzTdWHU8tPVZFaeGS+wFl2A/Nnb j6aSLSfLJPf1JqQhtE1RJe0YgvCYjXuNP0KWafe0YuNK0= X-Received: by 2002:a05:6a00:cd6:b0:82c:eafa:8875 with SMTP id d2e1a72fcca58-82f8c82e889mr32885163b3a.2.1777004916865; Thu, 23 Apr 2026 21:28:36 -0700 (PDT) Received: from pve-server ([49.205.216.49]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-82f8ebb33fcsm20983354b3a.33.2026.04.23.21.28.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Apr 2026 21:28:36 -0700 (PDT) From: Ritesh Harjani (IBM) To: Christian Brauner , lsf-pc@lists.linux-foundation.org, Jan Kara , Amir Goldstein Cc: Ojaswin Mujoo , Pankaj Raghav , Andres Freund , djwong@kernel.org, john.g.garry@oracle.com, willy@infradead.org, hch@lst.de, Luis Chamberlain , dchinner@redhat.com, Javier Gonzalez , gost.dev@samsung.com, tytso@mit.edu, p.raghav@samsung.com, vi.shah@samsung.com, linux-xfs@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org Subject: Re: [LSF/MM/BPF TOPIC] Buffered atomic writes In-Reply-To: Date: Fri, 24 Apr 2026 06:32:03 +0530 Message-ID: References: Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Hi Christian / LSF committee, > The preliminary schedule is accessible here: > https://docs.google.com/spreadsheets/d/1mGEdDrWskp7Ua91jGXzquQGinorcD58DAVXhOiRp2Gg/edit?gid=1852749899#gid=1852749899 > It just hasn't been liked on the website yet. Thanks for sharing the preliminary schedule. We had a discuss about this among us Me, Ojaswin, Pankaj and Andres too is on the same page. We were thinking if it is possible to extend the Buffered Atomic Write session into two "continuous" halves of 30mins each (total of 60mins)? Looks like in the past couple of months, there has been some good discussion & progress on this topic and we feel a 30min slot might not be enough to cover everything, since we want to give more time for QnA/Discussions. This is how we were thinking it might go: Buffered atomic write: Usecase & Discussion with Postgres I think in this slot Pankaj and Andres would like to cover: 1. Buffered atomic write usecases 2. How Postgres would like to use it and why is it important for them, ... 3. Q&A/Discussion @Pankaj / Andres - please add and/or correct if I missed anything in above. Buffered atomic write: The writethrough approach Ojaswin and I have been working on this and since a few approaches were tried, before we landed on the writethrough model, we think this may need a 30-minute slot of its own: So, I think Ojaswin can cover the following in this slot: 1. Briefly cover the previous 2 approaches on buffered atomic writes and what were the problems in those approaches. 2. Design of writethrough and its use beyond just support of buffered atomic writes. 3. Performance concern with the current approach (not sure if we will be able to get a thorough benchmarking numbers, but will try to share some initial data at least) 4. Q&A/Discussion Do you think this is possible? It will be best to keep both back to back, so that buffered writethrough can be discussed in continuation. -ritesh