OK, so before actually proceeding to understanding memories, let us in a sense of the internal features
or an internal architecture of, OK, so we have a CLB so configurable logic blocks and then inside
and Silvis, we have slices.
So we're finding out that approximately a third of the slices.
So what slices mean and what Yildiz will understand at the very end of our force.
But let us assume that CLB, something which is used to implement logic functions inside and SPG and
that logic function is implemented with the help of the slices.
So CLV is an abstract abstract.
You can see device or abstract feature or an abstract structure that can be used to implement an object
function.
And inside a CLV you have multiple slices.
So you'll be finding whenever we that in architecture.
So this is the case of Ladislav for seven keys architecture.
So we have all of the slices that slice and logic's slices.
So this can be used to implement the logic, whereas the rest of this is that slice emesis.
So this AMSANT used to implement a distributed memory.
So Slice L cells are used to implement analogical functions, whereas M used to implement or distributed
memories or in fact a memory.
So if you just go further you can actually see a calculation.
So these are the seeds of families and belonging to Spartan's seven.
And if you compare to the slices that you have in an architecture, approximately one third of slices
belongs to a memory and two thirds of the slices belongs to logic.
So you'll be finding this further restrict the amount of the memory that you can get out of a distributed.
Memory are distributed, right?
So usually the line that whenever you required a depth of that depth of one.
Twenty eight or less, you go with their distributed memory and with the date of it.
So if we just compare 72 students, you'd also be finding but let us assume that you are in a situation
where you want to exactly know what is the maximum size of distributed memory that I can get out of
a specific architecture or a maximum maximum size of a block of memory that I can get out of an architecture
so you can look at a specific activity.
So.
Inside Edition, we'll be finding that.
For an Arctic seven, the block which have the dedicated memory blocks available in an architecture,
can give us a memory of being and which is far, far, far high as compared to distributive memory.
And specifically the amount of memory that are distributed can provide assistance if we just go into
an Arctic seven, the world that we are using for this course.
So it'll be finding the EXI seven eight hundred feet will give us a maximum, distributed them to eighty
eight kids.
So this is the maximum distributed we can get out of the Arctic seven.
But always remember when you're required to have a small little memories you can use a slice em or specifically
LCD to implement or distributed memory.
But whenever your memory requirement is far more to the line, can can be set up as one twenty.
But also so if the debt is dipped is greater than 120, we usually prefer to go with a memory and we
give the and it is available for logic function.
And whenever the.
And the size is less than or the depth of the memory that is required is less than 120.
We specifically can go with the distributed memory if a resource vomitus.
Right.
So this is how you can use it to to significantly find out what is the maximum size that I can get out
of our distributed memory.
But usually if you have a larger memory requirement, you go with a memory.
If you have a smaller memory requirement, then you can cross over to the.