Re: disk I/O, VFS hirunningspace

Peter Jeremy wrote: Regarding vfs.lorunningspace and vfs.hirunningspace... On 2010-Jul-15 13:52:43 -0500, Alan Cox wrote: Keep in mind that we still run on some fairly small systems with limited I/O capabilities, e.g., a typical arm platform. More generally, with the range of systems that

Re: strange problem with int64_t variables

Em 2010.07.16. 12:17, pluknet escreveu: Almost the same (#__jid_t#jid_t#). Did you have to include any header for that? IIRC, I used __jid_t because it didn't compile with jid_t. The difference (and probably a trigger of bug elsewhere) might be in that this lives on amd64 arch (while yours

Re: strange problem with int64_t variables

On 16 July 2010 01:42, Gabor Kovesdan wrote: > Em 2010.07.13. 16:05, pluknet escreveu: >> >> #ifndef _SYS_SYSPROTO_H_ >> struct setjlimit_args { >>         jid_t   jid; >>         int     resource; >>         struct rlimit *rlp; >> }; >> #endif >> int >> setjlimit(td, uap) >>         struct thread

Re: disk I/O, VFS hirunningspace

Regarding vfs.lorunningspace and vfs.hirunningspace... On 2010-Jul-15 13:52:43 -0500, Alan Cox wrote: >Keep in mind that we still run on some fairly small systems with limited I/O >capabilities, e.g., a typical arm platform. More generally, with the range >of systems that FreeBSD runs on today,