Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268213AbUIGQw5 (ORCPT ); Tue, 7 Sep 2004 12:52:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268203AbUIGQtu (ORCPT ); Tue, 7 Sep 2004 12:49:50 -0400 Received: from maxipes.logix.cz ([81.0.234.97]:55475 "EHLO maxipes.logix.cz") by vger.kernel.org with ESMTP id S268157AbUIGQrK (ORCPT ); Tue, 7 Sep 2004 12:47:10 -0400 Date: Tue, 7 Sep 2004 18:47:06 +0200 (CEST) From: Michal Ludvig To: James Morris Cc: Greg KH , Andreas Happe , cryptoapi@lists.logix.cz, linux-kernel@vger.kernel.org Subject: Re: [cryptoapi/sysfs] display cipher details in sysfs In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 938 Lines: 24 On Tue, 7 Sep 2004, James Morris wrote: > On Sun, 5 Sep 2004, Greg KH wrote: > > > Other than that, I like this move, /proc/crypto isn't the best thing to > > have in a proc filesystem :) > > The only issue is what to do about potentially expanding this into an API > (e.g. open() an algorithm and write to it). Does this sort of thing > belong in sysfs? I already proposed to have a 'cryptoapifs' mounted e.g. under /dev/cryptoapi with the "active" entrypoints while /sys would only hold the "status" of the cryptoapi. Would this be a better approach? Michal Ludvig -- * A mouse is a device used to point at the xterm you want to type in. * Personal homepage - http://www.logix.cz/michal - 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/