On Tue, Aug 16, 2016 at 01:45:03PM -0700, J Freyensee wrote:
> On Mon, 2016-08-15 at 22:41 -0300, Helen Koike wrote:
> > struct nvmf_connect_command connect;
> > struct nvmf_property_set_command prop_set;
> > struct nvmf_property_get_command prop_get;
> > +
On Tue, Aug 16, 2016 at 01:45:03PM -0700, J Freyensee wrote:
> On Mon, 2016-08-15 at 22:41 -0300, Helen Koike wrote:
> > struct nvmf_connect_command connect;
> > struct nvmf_property_set_command prop_set;
> > struct nvmf_property_get_command prop_get;
> > +
On Mon, 2016-08-15 at 22:41 -0300, Helen Koike wrote:
>
> +struct nvme_doorbell_memory {
> + __u8opcode;
> + __u8flags;
> + __u16 command_id;
> + __u32 rsvd1[5];
> + __le64 prp1;
>
On Mon, 2016-08-15 at 22:41 -0300, Helen Koike wrote:
>
> +struct nvme_doorbell_memory {
> + __u8opcode;
> + __u8flags;
> + __u16 command_id;
> + __u32 rsvd1[5];
> + __le64 prp1;
>
From: Rob Nelson
This change provides a mechanism to reduce the number of MMIO doorbell
writes for the NVMe driver. When running in a virtualized environment
like QEMU, the cost of an MMIO is quite hefy here. The main idea for
the patch is provide the device two memory
From: Rob Nelson
This change provides a mechanism to reduce the number of MMIO doorbell
writes for the NVMe driver. When running in a virtualized environment
like QEMU, the cost of an MMIO is quite hefy here. The main idea for
the patch is provide the device two memory location locations:
1) to
6 matches
Mail list logo