lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CALKntY3_YuJxhJX7D5pZhD3pnsoSEz7E60ZTffHyF2W0Hu1fgw@mail.gmail.com>
Date:	Sat, 12 Nov 2011 13:08:06 -0500
From:	Xin Tong <xerox.time.tech@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Cost of a Page Fault

Hello All

   My research project in university involves building and using
custom processors as accerlerators. These processors are typically
hooked into the system via a PCIE bus. Applications are compiled with
the custom processor instruction set, when the x86 processor
encounters these extended instructions, it will fault and linux kernel
catches the fault and extract the custom processor instructions. While
extracting the custom processor instructions is not too difficult,
determining what memory the instructions are going to operate on is
hard. One of the ideas I have in mind is by copying the page table of
the faulty process to the custom processor. the custom processor has
its own MMU and when the MMU tries to find a page and the page is not
on the custom processor, it will generate a fault and a dma will be
initiated to copy over the page from system memory.

Therefore, I would like to know the typical time of a dma from system
memory to PCIE. It should be faster than a regular page fault because
regular page fault involves copying from disk which in theory should
be slower than PCIE devices.

Any comments on the cost of page fault and the project in general are
appreciated.

Thanks

Xin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ