From owner-freebsd-hackers@FreeBSD.ORG  Fri Jun 20 17:37:36 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 61EC737B401
	for <freebsd-hackers@freebsd.org>;
	Fri, 20 Jun 2003 17:37:36 -0700 (PDT)
Received: from hon.ai.univ-paris8.fr (hon.ai.univ-paris8.fr [192.33.156.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 134B543F3F
	for <freebsd-hackers@freebsd.org>;
	Fri, 20 Jun 2003 17:37:35 -0700 (PDT)
	(envelope-from mh@ai.univ-paris8.fr)
Received: from otake.ai.univ-paris8.fr (otake.ai.univ-paris8.fr
	[192.33.156.30])
	by hon.ai.univ-paris8.fr (8.12.9/8.12.8) with ESMTP id h5L0YpLr029779
	for <freebsd-hackers@freebsd.org>;
	Sat, 21 Jun 2003 02:34:51 +0200 (CEST)
Received: from localhost (mh@localhost)h5L1YKH266545
	for <freebsd-hackers@freebsd.org>;
	Sat, 21 Jun 2003 03:34:20 +0200 (WETDST)
Date: Sat, 21 Jun 2003 03:34:20 +0200
From: Marc Hufschmitt <mh@ai.univ-paris8.fr>
To: freebsd-hackers@freebsd.org
Message-ID: <Pine.SGI.4.51.0306210317210.266523@otake.ai.univ-paris8.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: networked block device
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jun 2003 00:37:36 -0000


I'm writing a remote block device on FreeBSD 4.6.2

As far as the network part is rather difficult, I don't want to include it
in the kernel module. So I started coding my module with this overall
structure in mind :

- a program reads the block device.

- the module receives read and write uio requests - no physio() nor
strategy() for now - and send them to a local daemon.

- the local daemon send the requests to remote daemons and data/status are
send back.

1. Am I wrong in the way to do it?

2. What is the clean way to pass the requests between module and local
client(s)?