From: David Miller <davem@davemloft.net>
To: sathya.perla@emulex.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] be2net: adding support for Lancer family of CNAs
Date: Sat, 27 Nov 2010 22:52:01 -0800 (PST) [thread overview]
Message-ID: <20101127.225201.112605958.davem@davemloft.net> (raw)
In-Reply-To: <20101122092550.GA11076@emulex.com>
From: Sathya Perla <sathya.perla@emulex.com>
Date: Mon, 22 Nov 2010 14:55:50 +0530
> Key changes are:
> - EQ ids are not assigned consecutively in Lancer. So, fix mapping of MSIx
> vector to EQ-id.
> - BAR mapping and some req locations different for Lancer.
> - TCP,UDP,IP checksum fields must be compulsorily set in TX wrb for TSO in
> Lancer.
> - CEV_IST reg not present in Lancer; so, peek into event queue to check for
> new entries
> - cq_create and mcc_create cmd interface is different for Lancer; handle
> accordingly
>
> Signed-off-by: Padmanabh Ratnakar <padmanabh.ratnakar@emulex.com>
> Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
Applied, thank you.
prev parent reply other threads:[~2010-11-28 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 9:25 [PATCH net-next-2.6] be2net: adding support for Lancer family of CNAs Sathya Perla
2010-11-28 6:52 ` 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=20101127.225201.112605958.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@emulex.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).