From: Govindarajulu Varadarajan <_govind@gmx.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: nalreddy@cisco.com, ssujith@cisco.com, benve@cisco.com,
Govindarajulu Varadarajan <_govind@gmx.com>
Subject: [PATCH 0/4 net-next] enic: add devcmd2
Date: Sun, 16 Aug 2015 01:44:50 +0530 [thread overview]
Message-ID: <1439669694-21744-1-git-send-email-_govind@gmx.com> (raw)
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.
Govindarajulu Varadarajan (4):
enic: move struct definition from .c to .h file
enic: use netdev_<foo> or dev_<foo> instead of pr_<foo>
enic: add devcmd2 resources
enic: add devcmd2
drivers/net/ethernet/cisco/enic/enic.h | 21 +-
drivers/net/ethernet/cisco/enic/enic_main.c | 5 +
drivers/net/ethernet/cisco/enic/vnic_cq.c | 3 +-
drivers/net/ethernet/cisco/enic/vnic_dev.c | 275 ++++++++++++++++++------
drivers/net/ethernet/cisco/enic/vnic_dev.h | 44 +++-
drivers/net/ethernet/cisco/enic/vnic_devcmd.h | 28 +++
drivers/net/ethernet/cisco/enic/vnic_intr.c | 3 +-
drivers/net/ethernet/cisco/enic/vnic_resource.h | 7 +
drivers/net/ethernet/cisco/enic/vnic_rq.c | 6 +-
drivers/net/ethernet/cisco/enic/vnic_wq.c | 31 ++-
drivers/net/ethernet/cisco/enic/vnic_wq.h | 17 ++
11 files changed, 357 insertions(+), 83 deletions(-)
--
2.5.0
next reply other threads:[~2015-08-15 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 20:14 Govindarajulu Varadarajan [this message]
2015-08-15 20:14 ` [PATCH 1/4 net-next] enic: move struct definition from .c to .h file Govindarajulu Varadarajan
2015-08-15 20:14 ` [PATCH 2/4 net-next] enic: use netdev_<foo> or dev_<foo> instead of pr_<foo> Govindarajulu Varadarajan
2015-08-15 20:14 ` [PATCH 3/4 net-next] enic: add devcmd2 resources Govindarajulu Varadarajan
2015-08-15 20:14 ` [PATCH 4/4 net-next] enic: add devcmd2 Govindarajulu Varadarajan
2015-08-17 22:38 ` [PATCH 0/4 " David Miller
2015-08-21 17:19 ` Brandeburg, Jesse
2015-08-21 18:40 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1439669694-21744-1-git-send-email-_govind@gmx.com \
--to=_govind@gmx.com \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=nalreddy@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=ssujith@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).