Re: [Nbd] [PATCH] Only send one reply on oversize writes
- To: Wouter Verhelst <w@...112...>
- Cc: nbd-general@lists.sourceforge.net
- Subject: Re: [Nbd] [PATCH] Only send one reply on oversize writes
- From: Alex Bligh <alex@...872...>
- Date: Sat, 28 May 2011 11:47:16 +0100
- Message-id: <5DA2DC50EEB2FE1A65B357A5@...874...>
- Reply-to: Alex Bligh <alex@...872...>
- In-reply-to: <20110528101214.GA9316@...510...>
- References: <1306560268-19484-1-git-send-email-alex@...872...> <20110528085523.GC32221@...510...> <33FC6E538A76BA35B1D798B4@...874...> <20110528101214.GA9316@...510...>
Wouter,
--On 28 May 2011 12:12:14 +0200 Wouter Verhelst <w@...112...> wrote:
What about a hash table instead? There's a GHashTable in libglib-2.0,
which we're already using.
That looks promising.
That would also allow reusing the original
handle number, which would make it slightly easier to match against
what's in the transaction log.
That won't work. Consider the original sequence
Request Reply
H1
H2
H2
H1
H1
H1
where H1 gets reused. I could (in fact probably would) replay this as
Request Reply
H1
H2
H1
H2
H1
H1
in which case there are 2 H1s in flight, and I won't be able to match
up the replies.
I could however use (e.g.) the seek offset as the handle, and store
the original handle.
--
Alex Bligh
Reply to: