On Wed, 12 May 2010 06:19:29 +0200
Justus Winter <4win...@informatik.uni-hamburg.de> wrote:
> And here are the results:
>
> Benchmarking /home/teythoon/ext2fs.vanilla...
> Running 'dd if=/dev/zero of=/mnt/sink bs=1M count=51'...
> 2.28 2.27 2.28 2.30 2.30 Average: 2.286
> Running 'tar xf /tmp/ramd
On Tue, 11 May 2010 19:19:01 +0200
Sergio Lopez wrote:
> Hi,
>
> I think short circuiting data_unlock requests in ext2fs (by allocating
> the page in file_pager_read_page and returning it unlocked) could
> improve file growing performance a bit.
>
> I've tested it in qemu (with kvm), using "dd"
Hello,
I do not have the time to try it myself, just commenting:
Da Zheng, le Tue 11 May 2010 09:35:34 +0800, a écrit :
> Linux drivers use jiffies to measure time. Unfortunately, Mach doesn't
> provide it
Mmm, but Mach's time device provides a read-only page where the current
time is available.
Da Zheng, le Sat 08 May 2010 23:19:08 +0800, a écrit :
> A stupid question: when disable_irq_nosync is called, IRQ_DISABLED is set in
> the
> irq descriptor in the Linux kernel and the corresponding hardirq line should
> be
> masked as well (at least, it seems the kernel for x86 does so).
AIUI,
Hi,
I think short circuiting data_unlock requests in ext2fs (by allocating
the page in file_pager_read_page and returning it unlocked) could
improve file growing performance a bit.
I've tested it in qemu (with kvm), using "dd" to sequentially write
blocks to a file, obtaining an improvement of 10
Hello,
When a memory object is being terminated (because a change in its
"can_persist" attribute or being cleaned from cache), GNU Mach calls
memory_object_terminate. This simpleroutine, sends Mach's receive
right on memory object control port to the external memory manager. In
Hurd, a translator
