Split block/character protocols and libdriver
This patch separates the character and block driver communication
protocols. The old character protocol remains the same, but a new
block protocol is introduced. The libdriver library is replaced by
two new libraries: libchardriver and libblockdriver. Their exposed
API, and drivers that use them, have been updated accordingly.
Together, libbdev and libblockdriver now completely abstract away
the message format used by the block protocol. As the memory driver
is both a character and a block device driver, it now implements its
own message loop.
The most important semantic change made to the block protocol is that
it is no longer possible to return both partial results and an error
for a single transfer. This simplifies the interaction between the
caller and the driver, as the I/O vector no longer needs to be copied
back. Also, drivers are now no longer supposed to decide based on the
layout of the I/O vector when a transfer should be cut short. Put
simply, transfers are now supposed to either succeed completely, or
result in an error.
After this patch, the state of the various pieces is as follows:
- block protocol: stable
- libbdev API: stable for synchronous communication
- libblockdriver API: needs slight revision (the drvlib/partition API
in particular; the threading API will also change shortly)
- character protocol: needs cleanup
- libchardriver API: needs cleanup accordingly
- driver restarts: largely unsupported until endpoint changes are
reintroduced
As a side effect, this patch eliminates several bugs, hacks, and gcc
-Wall and -W warnings all over the place. It probably introduces a
few new ones, too.
Update warning: this patch changes the protocol between MFS and disk
drivers, so in order to use old/new images, the MFS from the ramdisk
must be used to mount all file systems.
2011-11-22 13:27:53 +01:00
|
|
|
/* This file contains the singlethreaded device driver interface.
|
|
|
|
*
|
|
|
|
* Changes:
|
|
|
|
* Aug 27, 2011 extracted from driver.c (A. Welzel)
|
|
|
|
*
|
|
|
|
* The entry points into this file are:
|
|
|
|
* blockdriver_task: the main message loop of the driver
|
|
|
|
* blockdriver_terminate: break out of the main message loop
|
|
|
|
* blockdriver_handle_msg: handle a single received message
|
|
|
|
* blockdriver_receive_mq: message receive interface with message queueing
|
|
|
|
* blockdriver_mq_queue: queue an incoming message for later processing
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <minix/drivers.h>
|
|
|
|
#include <minix/blockdriver.h>
|
|
|
|
|
2011-12-07 15:44:28 +01:00
|
|
|
#include "const.h"
|
Split block/character protocols and libdriver
This patch separates the character and block driver communication
protocols. The old character protocol remains the same, but a new
block protocol is introduced. The libdriver library is replaced by
two new libraries: libchardriver and libblockdriver. Their exposed
API, and drivers that use them, have been updated accordingly.
Together, libbdev and libblockdriver now completely abstract away
the message format used by the block protocol. As the memory driver
is both a character and a block device driver, it now implements its
own message loop.
The most important semantic change made to the block protocol is that
it is no longer possible to return both partial results and an error
for a single transfer. This simplifies the interaction between the
caller and the driver, as the I/O vector no longer needs to be copied
back. Also, drivers are now no longer supposed to decide based on the
layout of the I/O vector when a transfer should be cut short. Put
simply, transfers are now supposed to either succeed completely, or
result in an error.
After this patch, the state of the various pieces is as follows:
- block protocol: stable
- libbdev API: stable for synchronous communication
- libblockdriver API: needs slight revision (the drvlib/partition API
in particular; the threading API will also change shortly)
- character protocol: needs cleanup
- libchardriver API: needs cleanup accordingly
- driver restarts: largely unsupported until endpoint changes are
reintroduced
As a side effect, this patch eliminates several bugs, hacks, and gcc
-Wall and -W warnings all over the place. It probably introduces a
few new ones, too.
Update warning: this patch changes the protocol between MFS and disk
drivers, so in order to use old/new images, the MFS from the ramdisk
must be used to mount all file systems.
2011-11-22 13:27:53 +01:00
|
|
|
#include "driver.h"
|
|
|
|
#include "mq.h"
|
|
|
|
|
|
|
|
PRIVATE int running;
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* blockdriver_receive_mq *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC int blockdriver_receive_mq(message *m_ptr, int *status_ptr)
|
|
|
|
{
|
|
|
|
/* receive() interface for drivers with message queueing. */
|
|
|
|
|
|
|
|
/* Any queued messages? */
|
2011-11-24 14:50:13 +01:00
|
|
|
if (mq_dequeue(SINGLE_THREAD, m_ptr, status_ptr))
|
Split block/character protocols and libdriver
This patch separates the character and block driver communication
protocols. The old character protocol remains the same, but a new
block protocol is introduced. The libdriver library is replaced by
two new libraries: libchardriver and libblockdriver. Their exposed
API, and drivers that use them, have been updated accordingly.
Together, libbdev and libblockdriver now completely abstract away
the message format used by the block protocol. As the memory driver
is both a character and a block device driver, it now implements its
own message loop.
The most important semantic change made to the block protocol is that
it is no longer possible to return both partial results and an error
for a single transfer. This simplifies the interaction between the
caller and the driver, as the I/O vector no longer needs to be copied
back. Also, drivers are now no longer supposed to decide based on the
layout of the I/O vector when a transfer should be cut short. Put
simply, transfers are now supposed to either succeed completely, or
result in an error.
After this patch, the state of the various pieces is as follows:
- block protocol: stable
- libbdev API: stable for synchronous communication
- libblockdriver API: needs slight revision (the drvlib/partition API
in particular; the threading API will also change shortly)
- character protocol: needs cleanup
- libchardriver API: needs cleanup accordingly
- driver restarts: largely unsupported until endpoint changes are
reintroduced
As a side effect, this patch eliminates several bugs, hacks, and gcc
-Wall and -W warnings all over the place. It probably introduces a
few new ones, too.
Update warning: this patch changes the protocol between MFS and disk
drivers, so in order to use old/new images, the MFS from the ramdisk
must be used to mount all file systems.
2011-11-22 13:27:53 +01:00
|
|
|
return OK;
|
|
|
|
|
|
|
|
/* Fall back to standard receive() interface otherwise. */
|
|
|
|
return driver_receive(ANY, m_ptr, status_ptr);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* blockdriver_terminate *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC void blockdriver_terminate(void)
|
|
|
|
{
|
|
|
|
/* Break out of the main driver loop after finishing the current request. */
|
|
|
|
|
|
|
|
running = FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* blockdriver_task *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC void blockdriver_task(struct blockdriver *bdp)
|
|
|
|
{
|
|
|
|
/* Main program of any block device driver task. */
|
|
|
|
int r, ipc_status;
|
|
|
|
message mess;
|
|
|
|
|
|
|
|
running = TRUE;
|
|
|
|
|
|
|
|
/* Here is the main loop of the disk task. It waits for a message, carries
|
|
|
|
* it out, and sends a reply.
|
|
|
|
*/
|
|
|
|
while (running) {
|
|
|
|
if ((r = blockdriver_receive_mq(&mess, &ipc_status)) != OK)
|
|
|
|
panic("blockdriver_receive_mq failed: %d", r);
|
|
|
|
|
|
|
|
blockdriver_process(bdp, &mess, ipc_status);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* blockdriver_process *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC void blockdriver_process(struct blockdriver *bdp, message *m_ptr,
|
|
|
|
int ipc_status)
|
|
|
|
{
|
|
|
|
/* Handle the given received message. */
|
|
|
|
int r;
|
|
|
|
|
|
|
|
/* Process the notification or request. */
|
|
|
|
if (is_ipc_notify(ipc_status)) {
|
|
|
|
blockdriver_handle_notify(bdp, m_ptr);
|
|
|
|
|
|
|
|
/* Do not reply to notifications. */
|
|
|
|
} else {
|
2011-11-24 14:50:13 +01:00
|
|
|
r = blockdriver_handle_request(bdp, m_ptr, SINGLE_THREAD);
|
Split block/character protocols and libdriver
This patch separates the character and block driver communication
protocols. The old character protocol remains the same, but a new
block protocol is introduced. The libdriver library is replaced by
two new libraries: libchardriver and libblockdriver. Their exposed
API, and drivers that use them, have been updated accordingly.
Together, libbdev and libblockdriver now completely abstract away
the message format used by the block protocol. As the memory driver
is both a character and a block device driver, it now implements its
own message loop.
The most important semantic change made to the block protocol is that
it is no longer possible to return both partial results and an error
for a single transfer. This simplifies the interaction between the
caller and the driver, as the I/O vector no longer needs to be copied
back. Also, drivers are now no longer supposed to decide based on the
layout of the I/O vector when a transfer should be cut short. Put
simply, transfers are now supposed to either succeed completely, or
result in an error.
After this patch, the state of the various pieces is as follows:
- block protocol: stable
- libbdev API: stable for synchronous communication
- libblockdriver API: needs slight revision (the drvlib/partition API
in particular; the threading API will also change shortly)
- character protocol: needs cleanup
- libchardriver API: needs cleanup accordingly
- driver restarts: largely unsupported until endpoint changes are
reintroduced
As a side effect, this patch eliminates several bugs, hacks, and gcc
-Wall and -W warnings all over the place. It probably introduces a
few new ones, too.
Update warning: this patch changes the protocol between MFS and disk
drivers, so in order to use old/new images, the MFS from the ramdisk
must be used to mount all file systems.
2011-11-22 13:27:53 +01:00
|
|
|
|
|
|
|
blockdriver_reply(m_ptr, ipc_status, r);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* blockdriver_mq_queue *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC int blockdriver_mq_queue(message *m, int status)
|
|
|
|
{
|
|
|
|
/* Queue a message for later processing. */
|
|
|
|
|
2011-11-24 14:50:13 +01:00
|
|
|
return mq_enqueue(SINGLE_THREAD, m, status);
|
Split block/character protocols and libdriver
This patch separates the character and block driver communication
protocols. The old character protocol remains the same, but a new
block protocol is introduced. The libdriver library is replaced by
two new libraries: libchardriver and libblockdriver. Their exposed
API, and drivers that use them, have been updated accordingly.
Together, libbdev and libblockdriver now completely abstract away
the message format used by the block protocol. As the memory driver
is both a character and a block device driver, it now implements its
own message loop.
The most important semantic change made to the block protocol is that
it is no longer possible to return both partial results and an error
for a single transfer. This simplifies the interaction between the
caller and the driver, as the I/O vector no longer needs to be copied
back. Also, drivers are now no longer supposed to decide based on the
layout of the I/O vector when a transfer should be cut short. Put
simply, transfers are now supposed to either succeed completely, or
result in an error.
After this patch, the state of the various pieces is as follows:
- block protocol: stable
- libbdev API: stable for synchronous communication
- libblockdriver API: needs slight revision (the drvlib/partition API
in particular; the threading API will also change shortly)
- character protocol: needs cleanup
- libchardriver API: needs cleanup accordingly
- driver restarts: largely unsupported until endpoint changes are
reintroduced
As a side effect, this patch eliminates several bugs, hacks, and gcc
-Wall and -W warnings all over the place. It probably introduces a
few new ones, too.
Update warning: this patch changes the protocol between MFS and disk
drivers, so in order to use old/new images, the MFS from the ramdisk
must be used to mount all file systems.
2011-11-22 13:27:53 +01:00
|
|
|
}
|