From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2EFD9383316; Mon, 28 Sep 2026 18:22:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790619765; cv=none; b=j1EnUEtfJxAL4lFta6xG618MUVzfeljhemQyYyJPT0IZnJF7n+Xr/A5OnqPzh0EuL8EUovV99DzzuUtOTH4lCugTe0r69GLPyh5NZbdiyWHUQOXhMsl4/WV07x94vFELYEiCCjoSu69PUgGtYbGlk47izkHnqZL4xxSNzTbCj10= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790619765; c=relaxed/simple; bh=K1cLWac03IM4KLKAmCbBaNPBWoO0bBv/YDS2Dcc186U=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=BJxaytBQCSJQiL4o3QIJvytuQlzBEcmqIkboX9u8Ir3tZc1dIQ7veNWpRNtZGVVHuqYc7LGDBOGb9WMBfswk4XHVwgItBHZBs9DtIEPSIyaba7pOyaJP0vUM2AzKczEkhnDhLT8p5Zt9MOOrdOAweclB5PlEh0xDo75M5prowfE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=jzRocgp9; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="jzRocgp9" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B04541F000FF; Mon, 28 Sep 2026 18:22:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790619763; bh=K1cLWac03IM4KLKAmCbBaNPBWoO0bBv/YDS2Dcc186U=; h=Date:Subject:Cc:To:From:References:In-Reply-To; b=jzRocgp9APFbn7PWm/lVftNBWm3nQuRe4DUsY1sk9cmMIiwjTgRQz3nzamHXngS9I D5vM+QVrBcWiDqiAKnqzhNEGR+VN4zBbJZRS+3RhDWZgRZHyyaOjXYKtHZ8UYogYlI xnP2x0peEeKDhrzkQMemQW6PZjv0TfneoPHS8XXrk+10ztob7MmG8VcIFgBndIwMmI X6rxeLZb1m7SDtl/JNvNQ2qRBw8oM1zCVVLFrw8dfMra73wGuHSIpl0DSNbBOHtJ2g gVsGur5H9GW6bmWAm67uLZpkNuy8XV/GVUc41PQrczztiKYMoML/svpOqrDftsFfIa MZbh+EkmNLKCw== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 28 Sep 2026 20:22:39 +0200 Message-Id: Subject: Re: [PATCH 2/2] rust: scatterlist: honor the device's maximum segment size Cc: "Alexandre Courbot" , "Matteo Kloiber" , "Robin Murphy" , , , , , , , , , , , , To: "Gary Guo" From: "Danilo Krummrich" References: <20260831233215.287881-1-kernel@matt3o12.de> <20260831233215.287881-3-kernel@matt3o12.de> <20260913210806.125589-1-kernel@matt3o12.de> <20260927224446.1053037-1-kernel@matt3o12.de> In-Reply-To: On Mon Sep 28, 2026 at 7:39 PM CEST, Gary Guo wrote: > I was quite skeptical whether the complication of adding the dma setup to= ken is > worth the effort, but the capacity struct sounds like a very nice design = as it's > infinitely extensible. I can foresee that we might want to eventually get= rid of > the special `Core` typestate and just replace everything with setup > capabilities. I had a similar thought (which is one of the reasons I proposed it), but I = don't think we can replace the Core type state entirely. There's more than just one bus callback that holds the Core type state, so = I think the bus setup token is rather the (much) better version of a Probe ty= pe state.