From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@qlogic.com
Cc: netdev@vger.kernel.org, Rajesh.Borundia@qlogic.com,
shyam.sundar@qlogic.com
Subject: Re: [PATCH net-next 0/4] qed: RocE & iSCSI infrastructure
Date: Fri, 03 Jun 2016 20:09:28 -0400 (EDT) [thread overview]
Message-ID: <20160603.200928.1525280019631601775.davem@davemloft.net> (raw)
In-Reply-To: <1464953735-2585-1-git-send-email-Yuval.Mintz@qlogic.com>
From: Yuval Mintz <Yuval.Mintz@qlogic.com>
Date: Fri, 3 Jun 2016 14:35:31 +0300
> We plan on sending 2 new protocol drivers in the imminent future -
> both our RoCE [qedr] and iSCSI [qedi] drivers. As both submissions
> would be rather massive and in order to avoid collisions between them,
> the common infrastructure on the qed side was prepared as an independent
> patch-series to be sent ahead of those 2 submissions.
>
> This patch series introduces in QED 2 new 'ids' - one for iscsi and
> one for roce. It then goes and adds logic required for configuring
> said protocols in HW. Notice it *doesn't* actually add any client using
> said ids, but rather only the infrastructure to allow their later usage.
>
> What this patch doesn't contain is the slowpath protocol-configuration
> toward the firmware. I.e., it contains register-setting logic, memory
> allocations, etc., but not actual flow-related configuration specific
> to the protocl. Those would be sent as part of the protocol driver
> submissions.
Series applied to net-next, thanks.
prev parent reply other threads:[~2016-06-04 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 11:35 [PATCH net-next 0/4] qed: RocE & iSCSI infrastructure Yuval Mintz
2016-06-03 11:35 ` [PATCH net-next 1/4] qed: Revisit chain implementation Yuval Mintz
2016-06-03 11:35 ` [PATCH net-next 2/4] qed: Add common HSI for new protocols Yuval Mintz
2016-06-03 11:35 ` [PATCH net-next 3/4] qed: Add iscsi/rdma personalities Yuval Mintz
2016-06-03 11:35 ` [PATCH net-next 4/4] qed: Initialize hardware for new protocols Yuval Mintz
2016-06-04 0:09 ` David Miller [this message]
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=20160603.200928.1525280019631601775.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Rajesh.Borundia@qlogic.com \
--cc=Yuval.Mintz@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=shyam.sundar@qlogic.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).