Re: [net-next v1 00/16] Device Memory TCP

2023-12-13 Thread Christoph Hellwig
On Wed, Dec 13, 2023 at 10:51:25PM -0800, Mina Almasry wrote: > On Wed, Dec 13, 2023 at 10:49 PM Christoph Hellwig wrote: > > > > On Thu, Dec 14, 2023 at 06:20:27AM +, > > patchwork-bot+netdev...@kernel.org wrote: > > > Hello: > > > > > > This series was applied to netdev/net-next.git (main)

Re: [net-next v1 00/16] Device Memory TCP

2023-12-13 Thread Mina Almasry
On Wed, Dec 13, 2023 at 10:49 PM Christoph Hellwig wrote: > > On Thu, Dec 14, 2023 at 06:20:27AM +, patchwork-bot+netdev...@kernel.org > wrote: > > Hello: > > > > This series was applied to netdev/net-next.git (main) > > by Jakub Kicinski : > > Umm, this is still very broken in intraction wit

Re: [net-next v1 00/16] Device Memory TCP

2023-12-13 Thread Christoph Hellwig
On Thu, Dec 14, 2023 at 06:20:27AM +, patchwork-bot+netdev...@kernel.org wrote: > Hello: > > This series was applied to netdev/net-next.git (main) > by Jakub Kicinski : Umm, this is still very broken in intraction with other subsystems. Please don't push ahead so quickly.

Re: [net-next v1 00/16] Device Memory TCP

2023-12-13 Thread patchwork-bot+netdevbpf
Hello: This series was applied to netdev/net-next.git (main) by Jakub Kicinski : On Thu, 7 Dec 2023 16:52:31 -0800 you wrote: > Major changes in v1: > -- > > 1. Implemented MVP queue API ndos to remove the userspace-visible >driver reset. > > 2. Fixed issues in the napi_pp_put_

Re: [net-next v1 00/16] Device Memory TCP

2023-12-11 Thread Christoph Hellwig
Please don't spread scatterlists further. They are a bad data structure that mix input data (page, offset, len) and output data (phys_addr, dma_offset, dma_len), and do in a horrible way for iommmu mappings that can coalesce. Jason and coworkers have been looking into the long overdue API to bett

Re: [net-next v1 00/16] Device Memory TCP

2023-12-09 Thread Shakeel Butt
On Thu, Dec 07, 2023 at 04:52:31PM -0800, Mina Almasry wrote: [...] > > Today, the majority of the Device-to-Device data transfers the network are 'the network' in above can be removed. > implemented as the following low level operations: Device-to-Host copy, > Host-to-Host network transfer, and

Re: [net-next v1 00/16] Device Memory TCP

2023-12-08 Thread Mina Almasry
On Fri, Dec 8, 2023 at 9:57 AM David Ahern wrote: > > On 12/7/23 5:52 PM, Mina Almasry wrote: > > Major changes in v1: > > -- > > > > 1. Implemented MVP queue API ndos to remove the userspace-visible > >driver reset. > > > > 2. Fixed issues in the napi_pp_put_page() devmem frag unr

Re: [net-next v1 00/16] Device Memory TCP

2023-12-08 Thread David Ahern
On 12/7/23 5:52 PM, Mina Almasry wrote: > Major changes in v1: > -- > > 1. Implemented MVP queue API ndos to remove the userspace-visible >driver reset. > > 2. Fixed issues in the napi_pp_put_page() devmem frag unref path. > > 3. Removed RFC tag. > > Many smaller addressed comme

Re: [net-next v1 00/16] Device Memory TCP

2023-12-07 Thread Mina Almasry
On Thu, Dec 7, 2023 at 4:52 PM Mina Almasry wrote: > > Major changes in v1: > -- > > 1. Implemented MVP queue API ndos to remove the userspace-visible >driver reset. > > 2. Fixed issues in the napi_pp_put_page() devmem frag unref path. > > 3. Removed RFC tag. > > Many smaller addre

[net-next v1 00/16] Device Memory TCP

2023-12-07 Thread Mina Almasry
Major changes in v1: -- 1. Implemented MVP queue API ndos to remove the userspace-visible driver reset. 2. Fixed issues in the napi_pp_put_page() devmem frag unref path. 3. Removed RFC tag. Many smaller addressed comments across all the patches (patches have individual change log