linux-kernel - Re: [PATCH 0/8] rados block device and ceph refactor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100813153706.ee61c94e.rdunlap@xenotime.net>
Date:	Fri, 13 Aug 2010 15:37:06 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Sage Weil <sage@...dream.net>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-scsi@...r.kernel.org, ceph-devel@...r.kernel.org, hch@....de,
	akpm@...ux-foundation.org, yehuda@...newdream.net
Subject: Re: [PATCH 0/8] rados block device and ceph refactor

On Fri, 13 Aug 2010 10:40:32 -0700 Sage Weil wrote:

> Hi,
> 
> The rados block device (rbd) implements a network block device backed by 
> the Ceph distributed object store (think nbd/iSCSI, but distributed and 
> fault tolerant).  At the suggestion of Christoph and James, this version 
> of the patchset factors out the common Ceph bits (the network protocol, 
> cluster membership, and object storage parts) into a libceph module 
> (currently in net/ceph/ and include/linux/ceph/) that is shared by the 
> file system component (fs/ceph) and rbd (drivers/block/rbd.c). The first 
> few patches lay some groundwork, #7 moves does the ceph -> libceph+ceph 
> split, and #8 adds the block device driver.

Hi,
Did patch #7 make it to any mailing lists?
I didn't receive it.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/