1 / 18

CS Honors Research: Memory Mapped files in Linux Results

CS Honors Research: Memory Mapped files in Linux Results. Kousha Najafi Prof: Eddie Kohler Grad Student: Steve VanDeBogart 6.6.08. Research Topic. Explore Linux memory-mapped-file system call performance. Find and classify inconsistencies when compared to read system call.

gay
Download Presentation

CS Honors Research: Memory Mapped files in Linux Results

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS Honors Research:Memory Mapped files in LinuxResults Kousha Najafi Prof: Eddie Kohler Grad Student: Steve VanDeBogart 6.6.08

  2. Research Topic • Explore Linux memory-mapped-file system call performance. • Find and classify inconsistencies when compared to read system call

  3. mmap vs read (Forwards old) Reading 256MB file on system with 128MB memory

  4. mmap vs read (Forwards) Reading 256MB file on system with 128MB memory

  5. mmap vs read (Backwards old) Reading 256MB file on system with 128MB memory

  6. mmap vs read (Backwards) Reading 256MB file on system with 128MB memory

  7. Progress • Figure out what causes the inconsistencies • Inconsistencies in timing fixed by slowing down algorithm. • Figure out what causes the slowdown • Slowdown caused by pauses in io • Slowdown and inconsistencies are related

  8. Methods of attack • Jump in and investigate source • Used small test programs to show ideas • Good progress in beginning • Reached a brick wall • Expanded test suit to cover more cases • Strengthened code to include more cases

  9. Methods of attack (Continued) • Started to simulate algorithm • Started with block traces • Block traces looked very similar • The real problem showed itself…

  10. Forwards Blocktrace

  11. Forwards read zoom

  12. Forwards mmap zoom

  13. Backwards Blocktrace

  14. Backward read zoom

  15. Backward mmap zoom

  16. Conclusions • Inconsistencies and slowdowns appear to be due to io disk scheduler • More tests need to be done with various modifications kernels to further isolate problem

More Related