diff options
| author | Stefano Stabellini <sstabellini@kernel.org> | 2017-01-03 17:28:44 +0100 |
|---|---|---|
| committer | Greg Kurz <groug@kaod.org> | 2017-01-03 17:28:44 +0100 |
| commit | 88da0b03019ecadc3faaddf81a97c7ac83448280 (patch) | |
| tree | fcca3c515af1e53758118e2edf9635bcc17a0321 /hw/9pfs/9p.h | |
| parent | bcb8998fac16a7f26ac9cc3637e17701cfe69e5b (diff) | |
9pfs: introduce init_out/in_iov_from_pdu
Not all 9pfs transports share memory between request and response. For
those who don't, it is necessary to know how much memory is required in
the response.
Split the existing init_iov_from_pdu function in two:
init_out_iov_from_pdu (for writes) and init_in_iov_from_pdu (for reads).
init_in_iov_from_pdu takes an additional size parameter to specify the
memory required for the response message.
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Greg Kurz <groug@kaod.org>
Diffstat (limited to 'hw/9pfs/9p.h')
| -rw-r--r-- | hw/9pfs/9p.h | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/hw/9pfs/9p.h b/hw/9pfs/9p.h index c8c9aa8909..4c4feafa2e 100644 --- a/hw/9pfs/9p.h +++ b/hw/9pfs/9p.h @@ -349,8 +349,10 @@ struct V9fsTransport { va_list ap); ssize_t (*pdu_vunmarshal)(V9fsPDU *pdu, size_t offset, const char *fmt, va_list ap); - void (*init_iov_from_pdu)(V9fsPDU *pdu, struct iovec **piov, - unsigned int *pniov, bool is_write); + void (*init_in_iov_from_pdu)(V9fsPDU *pdu, struct iovec **piov, + unsigned int *pniov, size_t size); + void (*init_out_iov_from_pdu)(V9fsPDU *pdu, struct iovec **piov, + unsigned int *pniov); void (*push_and_notify)(V9fsPDU *pdu); }; |