On Fri, Mar 29, 2013 at 04:57:48PM -0700, Maksim Yevmenkin wrote:
On Fri, Mar 29, 2013 at 1:58 PM, Konstantin Belousov
kostik...@gmail.com wrote:
I think this is definitely a feature that should be set by a flag to
either file descriptor used for aio_read, or aio_read call itself.
Adding a
On Sat, Mar 30, 2013 at 01:51:15AM -0600, Scott Long wrote:
On Mar 29, 2013, at 2:58 PM, Konstantin Belousov kostik...@gmail.com wrote:
I think this is definitely a feature that should be set by a flag to
either file descriptor used for aio_read, or aio_read call itself.
Adding a
On Mar 29, 2013, at 2:58 PM, Konstantin Belousov kostik...@gmail.com wrote:
I think this is definitely a feature that should be set by a flag to
either file descriptor used for aio_read, or aio_read call itself.
Adding a flag to aio_read() might be cumbersome from the ABI perspective.
On Thu, Mar 28, 2013 at 10:11:25AM -0700, Maksim Yevmenkin wrote:
On Thu, Mar 28, 2013 at 12:52 AM, Konstantin Belousov
kostik...@gmail.com wrote:
i would like to get some reviews, opinions and/or comments on the patch
below.
a little bit background, as far as i understand,
On Fri, Mar 29, 2013 at 1:58 PM, Konstantin Belousov
kostik...@gmail.com wrote:
On Thu, Mar 28, 2013 at 10:11:25AM -0700, Maksim Yevmenkin wrote:
On Thu, Mar 28, 2013 at 12:52 AM, Konstantin Belousov
kostik...@gmail.com wrote:
i would like to get some reviews, opinions and/or comments on the
On Wed, Mar 27, 2013 at 01:43:32PM -0700, Maksim Yevmenkin wrote:
Hello,
i would like to get some reviews, opinions and/or comments on the patch below.
a little bit background, as far as i understand, cluster_read() can
initiate two disk i/o's: one for exact amount of data being requested
... you guys should think about writing an aio_sendfile() function for FreeBSD.
Just saying.
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
Hello,
i would like to get some reviews, opinions and/or comments on the patch below.
a little bit background, as far as i understand, cluster_read() can
initiate two disk i/o's: one for exact amount of data being requested
(rounded up to a filesystem block size) and another for a configurable