Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755953Ab0KLRtu (ORCPT ); Fri, 12 Nov 2010 12:49:50 -0500 Received: from mail-ew0-f46.google.com ([209.85.215.46]:39404 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751829Ab0KLRts convert rfc822-to-8bit (ORCPT ); Fri, 12 Nov 2010 12:49:48 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MK4dTZJtoZM3wf34UC+/v8CY/nwlR04nwovML05auWV/Q6sD2lzCxdu8ZNMPZP/6t9 Lyn6ZEVHAw9OsFSkVFeXnE0wmBMC0zriwJhc9WP/7JMTQUPxFjqw6x/1Lr4T61SBHwAq 9JzOAFG1ObGk6RoZsiAwHwZshcQIFpHkGCsw4= MIME-Version: 1.0 In-Reply-To: References: <20101106050721.GA2194@kroah.com> <20101111010841.GA23127@kroah.com> Date: Fri, 12 Nov 2010 09:49:46 -0800 Message-ID: Subject: Re: [RFC] rbd sysfs interface From: Yehuda Sadeh Weinraub To: Greg KH Cc: ceph-devel@vger.kernel.org, Sage Weil , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1833 Lines: 53 On Wed, Nov 10, 2010 at 9:16 PM, Yehuda Sadeh Weinraub wrote: > On Wed, Nov 10, 2010 at 5:08 PM, Greg KH wrote: >> >> So, back to sysfs. ?But I can't recall what your sysfs interface looked >> like, do you have Documentation/ABI/ files that show what it does? ?If >> not, you are required to, so you might as well write them now :) >> > > The original sysfs interface is described in the rbd.c prefix > comments, which we can copy to Documentation/ABI without much pain. > However, we were just thinking of modifying it a bit, as described > previously in my first email. The hierarchy will look like this: > > rbd/ > ? ?add > ? ?remove > ? ?/ > ? ? ?name > ? ? ?pool > ? ? ?size > ? ? ?.. > ? ? ?snap_add > ? ? ?snap_remove > ? ? ?snap_rollback > ? ? ? ?/ > ? ? ? ? ?size > > The 'add' entry will be used to add a device (as before): > > ?# echo "10.0.0.1 name=admin rbd myimage" > /sys/class/rbd/add > > The devices that'll be created still be enumerated, and there'll be a > subdirectory under rbd/ for each (actually a soft link to > /sys/devices/virtual/rbd/). For each device we'll have multiple > read-only properties (name, pool, size, client_id, major, cur_snap) > and a few control entries (e.g., snap_add, snap_remove, etc.) > > There will be a subdirectory per snapshot under each device, and all > the snapshots properties will be kept there. > Unless I hear otherwise, I'm going to assume that this proposed interface is an improvement over the existing osdblk-based one and get this upstream asap.. Thanks, Yehuda -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/