PC Lab 5 - Revizia istoricului

Cbira la 19 aprilie 2018 16:04

2018-04-19T16:04:10Z

Cbira la 19 aprilie 2018 15:19

2018-04-19T15:19:14Z

Cbira la 14 aprilie 2018 09:17

2018-04-14T09:17:07Z

Cbira la 14 aprilie 2018 09:16

2018-04-14T09:16:37Z

Cbira la 14 aprilie 2018 09:12

2018-04-14T09:12:59Z

Cbira la 14 aprilie 2018 09:12

2018-04-14T09:12:08Z

Cbira la 14 aprilie 2018 09:09

2018-04-14T09:09:35Z

Cbira la 14 aprilie 2018 09:09

2018-04-14T09:09:16Z

Cbira la 14 aprilie 2018 09:07

2018-04-14T09:07:13Z

Cbira la 14 aprilie 2018 09:03

2018-04-14T09:03:13Z

← Versiunea anterioară		Versiunea de la data 19 aprilie 2018 16:04
Linia 44:		Linia 44:

	DESCRIBE_INSTR = Write as function prototype with result, name, operand number, types and size (similar to Intel Intrinsics Guide). Write a natural-language description of the behaviour (or alternatively, the formal description as in Intel Intrinsics Guide)		DESCRIBE_INSTR = Write as function prototype with result, name, operand number, types and size (similar to Intel Intrinsics Guide). Write a natural-language description of the behaviour (or alternatively, the formal description as in Intel Intrinsics Guide)
		+
		+
		+	[[Fișier:Callgrind.out.20485.zip]]

@@ Linia 20: / Linia 20: @@
 kcachegrind whateverprofile.callgrind // open profile.callgrind with kcachegrind
-'''5.''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much time is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 MB/s. Hint: Use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send results/comments/snapshot(s) by e-mail to the teacher.
+'''5.''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much time is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 GB/s. Hint: Use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send results/comments/snapshot(s) by e-mail to the teacher.
 '''Note''': Valgrind is also great for checking memory leaks:

← Versiunea anterioară		Versiunea de la data 14 aprilie 2018 09:17
Linia 43:		Linia 43:
	5 points for identifying 1 most-heavy leaf-functions and coarse (within 50%) computation for offloading impact. DESCRIBE_INSTR.		5 points for identifying 1 most-heavy leaf-functions and coarse (within 50%) computation for offloading impact. DESCRIBE_INSTR.

−	DESCRIBE_INSTR = Write as function prototype with result, name, operand number, types and size (similar to Intel Intrinsics Guide). Write a natural-language description of the behaviour (or ~~alternative-le~~, the formal description as in Intel Intrinsics Guide)	+	DESCRIBE_INSTR = Write as function prototype with result, name, operand number, types and size (similar to Intel Intrinsics Guide). Write a natural-language description of the behaviour (or alternatively, the formal description as in Intel Intrinsics Guide)

@@ Linia 31: / Linia 31: @@
 '''Points (out of 10) vs. expected performance''':
-points for identifying 3 most-heavy leaf-functions and correct (within 10%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.
+points for identifying 3 most-heavy leaf-functions and correct (within 10%) computation for offloading impact. DESCRIBE_INSTR.
-points for identifying 3 most-heavy leaf-functions and acceptable (within 20%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.
+points for identifying 3 most-heavy leaf-functions and acceptable (within 20%) computation for offloading impact. DESCRIBE_INSTR.
-points for identifying 2 most-heavy leaf-functions and correct (within 10%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.
+points for identifying 2 most-heavy leaf-functions and correct (within 10%) computation for offloading impact. DESCRIBE_INSTR.
-points for identifying 2 most-heavy leaf-functions and resonable (within 30%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.
+points for identifying 2 most-heavy leaf-functions and resonable (within 30%) computation for offloading impact. DESCRIBE_INSTR.
-points for identifying 1 most-heavy leaf-functions and resonable (within 30%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.
+points for identifying 1 most-heavy leaf-functions and resonable (within 30%) computation for offloading impact. DESCRIBE_INSTR.
-points for identifying 1 most-heavy leaf-functions and coarse (within 50%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.
+points for identifying 1 most-heavy leaf-functions and coarse (within 50%) computation for offloading impact. DESCRIBE_INSTR.

@@ Linia 20: / Linia 20: @@
 kcachegrind whateverprofile.callgrind // open profile.callgrind with kcachegrind
-'''5''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much time is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 MB/s. Hint: Use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send results/comments/snapshot(s) by e-mail to the teacher.
+'''5.''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much time is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 MB/s. Hint: Use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send results/comments/snapshot(s) by e-mail to the teacher.
 '''Note''': Valgrind is also great for checking memory leaks:

← Versiunea anterioară		Versiunea de la data 14 aprilie 2018 09:09
Linia 29:		Linia 29:


−	Points (out of 10) vs. expected performance:	+	'''Points (out of 10) vs. expected performance''':

	10 points for identifying 3 most-heavy leaf-functions and correct (within 10%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.		10 points for identifying 3 most-heavy leaf-functions and correct (within 10%) computation for offloading impact. Describe the required instruction(s) of the coprocessor.

@@ Linia 20: / Linia 20: @@
 kcachegrind whateverprofile.callgrind // open profile.callgrind with kcachegrind
-'''5''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 MB/s. Hint: use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send result and snapshot(s) to the teacher.
+'''5''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much time is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 MB/s. Hint: Use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send result/comments/snapshot(s) to the teacher.
 '''Note''': Valgrind is also great for checking memory leaks:
@@ Linia 37: / Linia 29: @@
-Points (out of 10) vs. expected performance ():
+Points (out of 10) vs. expected performance:
-TBD
+points for identifying 1 most-heavy leaf-functions and coarse (within 50%) computation for offloading impact.

← Versiunea anterioară		Versiunea de la data 14 aprilie 2018 09:03
Linia 22:		Linia 22:
	'''5''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 MB/s. Hint: use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send result and snapshot(s) to the teacher.		'''5''' Look over the report, and propose 3 leaf-functions (functions that do not call other functions) for offloading towards a coprocessor. Write the reason for choosing each of them, and how much is gained by offloading them. Assume coprocessor works at infinite clock, but data is transferred at 200 MB/s. Hint: use the callgraph (by installing the graphiviz package). Keep a snapshot with the analysis report as proof. Send result and snapshot(s) to the teacher.

		+	'''6'''
		+	10 / 10 points for identifying 3 most-heavy leaf-functions and correct (within 10%) computation for offloading impact.
		+	9 / 10 points for identifying 3 most-heavy leaf-functions and correct (within 20%) computation for offloading impact.
		+	8 / 10 points for identifying 2 most-heavy leaf-functions and correct (within 10%) computation for offloading impact.
		+	7 / 10 points for identifying 2 most-heavy leaf-functions and correct (within 30%) computation for offloading impact.
		+	6 / 10 points for identifying 1 most-heavy leaf-functions and correct (within 30%) computation for offloading impact.
		+	5 / 10 points for identifying 1 most-heavy leaf-functions and correct (within 50%) computation for offloading impact.

	'''Note''': Valgrind is also great for checking memory leaks:		'''Note''': Valgrind is also great for checking memory leaks: