On Fri, May 22, 2015 at 10:22 AM, Parav Pandit
wrote:
> On Fri, May 22, 2015 at 2:15 AM, J Freyensee
> wrote:
>> On Wed, 2015-05-20 at 16:43 -0400, Parav Pandit wrote:
>>> nvme_queue structure made 64B cache friendly so that majority of the
>>> data elements of the structure during IO and complet
On Fri, May 22, 2015 at 2:15 AM, J Freyensee
wrote:
> On Wed, 2015-05-20 at 16:43 -0400, Parav Pandit wrote:
>> nvme_queue structure made 64B cache friendly so that majority of the
>> data elements of the structure during IO and completion path can be
>> found in typical single 64B cache line size
On Wed, 2015-05-20 at 16:43 -0400, Parav Pandit wrote:
> nvme_queue structure made 64B cache friendly so that majority of the
> data elements of the structure during IO and completion path can be
> found in typical single 64B cache line size which was previously spanning
> beyond single 64B cache l
nvme_queue structure made 64B cache friendly so that majority of the
data elements of the structure during IO and completion path can be
found in typical single 64B cache line size which was previously spanning
beyond single 64B cache line size.
By aligning most of the fields are found at start of
4 matches
Mail list logo