Re: [LSF/MM TOPIC] copy offloading

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2014-01-15 at 12:27 -0800, Zach Brown wrote:
> Discussing copy offloading at LSF is appropriate because it can involve
> so many layers of the stack:
> 
>  - high level syscall interface
>  - in-kernel high level entry point for nfsd 
>  - fs specific implementations (btrfs and ocfs2 cow, nfs) 
>  - vfs helper for offloading block copies for ext*,xfs
>  - bio offload requests for cow block devices like bcache/dm-cache
>  - encoding offload bios into scsi reqs
>  - processing virt guest device offload requests with host syscalls
> 
> Getting the user and in-kernel interfaces right to support all these
> moving parts has proven tricky.  The more input, the better.
> 
> It's been a while since I sent out a refreshed version of the series.
> That'll be remedied before LSF rolls around :). 
> 

+1

Now that EXTENDED_COPY LID1 target mode logic is upstream, I'm really
eager to start utilizing it Linux host side.  ;)

--nab

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux