On Apr 12, 11:32 pm, Senthil Raja wrote:
> Will get the following error "attempting to read from closed socket", while
> max connection is reached.
Is there a different error you'd rather get when you exceed the
limits you've specified?
--
To unsubscribe, reply using "remove me" as the sub
Hi,,
Will get the following error "attempting to read from closed socket", while
max connection is reached.
Regards
N.SenthilRaja.
--
To unsubscribe, reply using "remove me" as the subject.
On 1. apr. 2010, at 22.31, KaiGai Kohei wrote:
>
> $ git diff origin/reworks_2 origin/reworks_3
> -> It adds the 'features' field at engine_interface structure, to
>inform what features are supported by the loaded module.
I couldn't see this branch anymore, but I pushed a proposal for this
On 12. apr. 2010, at 02.18, KaiGai Kohei wrote:
> Are you saying the data fragments are not necessary to be placed on the
> continuous region in physically?
> If so, it seems to me allocate() method needs to be revised to take an
> arguments to indicate the number of fragments (with their lengths
(2010/04/12 16:24), Trond Norbye wrote:
>
> On 11. apr. 2010, at 17.56, KaiGai Kohei wrote:
>>
>> It seems to me the new get_item_info() interface intends to contain various
>> kind of properties more than bare threes (value, cas and expired time),
>> because we can easily expand the number of 'st
On 11. apr. 2010, at 17.56, KaiGai Kohei wrote:
>
> It seems to me the new get_item_info() interface intends to contain various
> kind of properties more than bare threes (value, cas and expired time),
> because we can easily expand the number of 'struct iovec value[]' in the
> new item_info.
>
