Home
last modified time | relevance | path

Searched hist:eabba580 (Results 1 – 3 of 3) sorted by relevance

/qemu/block/
H A Dqed.heabba580 Mon Dec 06 16:08:02 GMT 2010 Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> qed: Read/write support

This patch implements the read/write state machine. Operations are
fully asynchronous and multiple operations may be active at any time.

Allocating writes lock tables to ensure metadata updates do not
interfere with each other. If two allocating writes need to update the
same L2 table they will run sequentially. If two allocating writes need
to update different L2 tables they will run in parallel.

Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
H A Dqed.ceabba580 Mon Dec 06 16:08:02 GMT 2010 Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> qed: Read/write support

This patch implements the read/write state machine. Operations are
fully asynchronous and multiple operations may be active at any time.

Allocating writes lock tables to ensure metadata updates do not
interfere with each other. If two allocating writes need to update the
same L2 table they will run sequentially. If two allocating writes need
to update different L2 tables they will run in parallel.

Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
/qemu/
H A Dtrace-eventseabba580 Mon Dec 06 16:08:02 GMT 2010 Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> qed: Read/write support

This patch implements the read/write state machine. Operations are
fully asynchronous and multiple operations may be active at any time.

Allocating writes lock tables to ensure metadata updates do not
interfere with each other. If two allocating writes need to update the
same L2 table they will run sequentially. If two allocating writes need
to update different L2 tables they will run in parallel.

Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>