From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] aio_cancel/3-1: increase BUF_SIZE
Date: Wed, 11 Apr 2012 19:30:16 +0800 [thread overview]
Message-ID: <4F856B48.2060101@cn.fujitsu.com> (raw)
In-Reply-To: <4F855A0D.9010308@casparzhang.com>
On 04/11/2012 06:16 PM, Caspar Zhang wrote:
> On 04/11/2012 04:40 PM, Kang Kai wrote:
>> When do aio_cancel, all the aio_write operations have finished on some
>> platforms. That cause the case return UNRESOLVED. So increase the BUF_SIZE
>> to delay aio_write finish that make one aio_write operation can be
>> cancelled at least.
>>
>> Signed-off-by: Kang Kai <kai.kang@windriver.com>
> Reviewed-by: Caspar Zhang <caspar@casparzhang.com>
pushed, thanks all,
Wanlong Gao
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-04-11 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 8:40 [LTP] [PATCH] aio_cancel/3-1: increase BUF_SIZE Kang Kai
2012-04-11 10:16 ` Caspar Zhang
2012-04-11 11:30 ` Wanlong Gao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F856B48.2060101@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=Kai.Kang@windriver.com \
--cc=ltp-list@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.