On Jan 3 10:40, Christopher Faylor wrote:
> On Wed, Jan 03, 2007 at 02:35:57PM +0100, Corinna Vinschen wrote:
> >On Jan 3 06:20, Eric Blake wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> According to Corinna Vinschen on 1/3/2007 5:16 AM:
> >> >
> >> > Setting st_blksiz
On Wed, 3 Jan 2007, Corinna Vinschen wrote:
> So it appears to make much sense to set the blocksize to 64K.
blocksize is not really the proper term here as it is very confusing.
Preferred or optimal I/O size is a better choice in my opinion.
> The only question would be whether to use getpagesiz
On Wed, 3 Jan 2007, Eric Blake wrote:
> coreutils has the following, in src/system.h, used by cp, install, mv, du,
> ls, stat...
[snip]
> For example, in cp, the following usage appears:
[snip]
> It sounds like we want to ensure that cygwin chooses ST_BLKSIZE at 64k
> (optimal I/O size) but ST_NBL
On Wed, Jan 03, 2007 at 02:35:57PM +0100, Corinna Vinschen wrote:
>On Jan 3 06:20, Eric Blake wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> According to Corinna Vinschen on 1/3/2007 5:16 AM:
>> >
>> > Setting st_blksize to 64K might be a good idea for disk I/O if the value
>>
On Jan 3 06:20, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Corinna Vinschen on 1/3/2007 5:16 AM:
> >
> > Setting st_blksize to 64K might be a good idea for disk I/O if the value
> > is actually used by applications. Do you have a specific example or a
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 1/3/2007 5:16 AM:
>
> Setting st_blksize to 64K might be a good idea for disk I/O if the value
> is actually used by applications. Do you have a specific example or a
> test result from a Cygwin application which show
On Jan 2 13:49, Brian Ford wrote:
> On Tue, 2 Jan 2007, Christopher Faylor wrote:
>
> > I don't see how replacing the constant "S_BLKSIZE" with what seems to be
> > an unrelated getpagesize () makes a lot of sense.
>
> The st_blksize field represents the preferred I/O size (in bytes) for the
> c
