From: David Miller <davem@davemloft.net>
To: hariprasad@chelsio.com
Cc: netdev@vger.kernel.org, leedom@chelsio.com, nirranjan@chelsio.com
Subject: Re: [PATCH net 0/3] cxgb4/cxgb4vf: Misc. fixes for cxgb4vf
Date: Mon, 10 Nov 2014 14:15:53 -0500 (EST) [thread overview]
Message-ID: <20141110.141553.69503749630771413.davem@davemloft.net> (raw)
In-Reply-To: <1415360191-25395-1-git-send-email-hariprasad@chelsio.com>
From: Hariprasad Shenai <hariprasad@chelsio.com>
Date: Fri, 7 Nov 2014 17:06:28 +0530
> For T5 use Packing and Padding Boundaries for SGE DMA transfers, move
> fl_starve_thres to adpater structure, since they are different for each
> adapter. The cxgb4vf driver's Free List Starvation Threshold needs to be larger
> than the SGE's Egress Congestion Threshold or we'll end up in a mutual stall
> where the driver waits for Ingress Packets to drive replacing Free List
> Pointers and the SGE waits for Free List Pointers before pushing Ingress
> Packets to the host.
>
> The patches series is created against 'net' tree.
> And includes patches on cxgb4 and cxgb4vf driver.
>
> We have included all the maintainers of respective drivers. Kindly review the
> change and let us know in case of any review comments.
Series applied, thanks.
prev parent reply other threads:[~2014-11-10 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:36 [PATCH net 0/3] cxgb4/cxgb4vf: Misc. fixes for cxgb4vf Hariprasad Shenai
2014-11-07 11:36 ` [PATCH net 1/3] cxgb4vf: Move fl_starv_thres into adapter->sge data structure Hariprasad Shenai
2014-11-07 11:36 ` [PATCH net 2/3] cxgb4/cxgb4vf: For T5 use Packing and Padding Boundaries for SGE DMA transfers Hariprasad Shenai
2014-11-07 11:36 ` [PATCH net 3/3] cxgb4vf: FL Starvation Threshold needs to be larger than the SGE's Egress Congestion Threshold Hariprasad Shenai
2014-11-10 19:15 ` 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=20141110.141553.69503749630771413.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=leedom@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.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