[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150817.153832.1220000969996122058.davem@davemloft.net>
Date: Mon, 17 Aug 2015 15:38:32 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: _govind@....com
Cc: netdev@...r.kernel.org, nalreddy@...co.com, ssujith@...co.com,
benve@...co.com
Subject: Re: [PATCH 0/4 net-next] enic: add devcmd2
From: Govindarajulu Varadarajan <_govind@....com>
Date: Sun, 16 Aug 2015 01:44:50 +0530
> This series adds new devcmd2 support. The first two patches are code
> refactoring.
>
> devcmd is an interface for driver to communicate with fw/adaptor. It
> involves writing data to hardware registers and waiting for the result.
> This mechanism does not scale well. The queuing of "no wait" devcmds is
> done in firmware memory rather than on the host. Firmware memory is a
> rather more scarce and valuable resource than host memory. A devcmd storm
> from one vf can disrupt the service on other pf/vf. The lack of flow
> control allows for possible denial of server from one VM to another.
> Devcmd2 uses work queue to post the devcmds, just like tx work queue. This
> allows better flow control.
Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists