On Mon, May 15, 2017 at 12:15:28PM +0300, Sagi Grimberg wrote:
>
> > > Hi,
>
> Hi Oza,
>
> > > we are configuring interrupt coalesce for NVMe, but right now, it uses
> > > module param.
> > > so the same interrupt coalesce settings get applied for all the NVMEs
> > > connected to different RCs.
On Mon, May 15, 2017 at 2:45 PM, Sagi Grimberg wrote:
>
>>> Hi,
>
>
> Hi Oza,
>
>>> we are configuring interrupt coalesce for NVMe, but right now, it uses
>>> module param.
>>> so the same interrupt coalesce settings get applied for all the NVMEs
>>> connected to different RCs.
>>>
>>> ideally it
Hi,
Hi Oza,
we are configuring interrupt coalesce for NVMe, but right now, it uses
module param.
so the same interrupt coalesce settings get applied for all the NVMEs
connected to different RCs.
ideally it should be with sysctl.
If at all, I would place this in nvme-cli (via ioctl) instea
On Mon, May 15, 2017 at 2:04 PM, Oza Oza wrote:
> Hi,
>
> we are configuring interrupt coalesce for NVMe, but right now, it uses
> module param.
> so the same interrupt coalesce settings get applied for all the NVMEs
> connected to different RCs.
>
> ideally it should be with sysctl.
> for e.g.
>
4 matches
Mail list logo