netdev - [PATCH net-next 0/5] cxgb4: Misc. fixes for sge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1429043554-8744-1-git-send-email-hariprasad@chelsio.com>
Date:	Wed, 15 Apr 2015 02:02:29 +0530
From:	Hariprasad Shenai <hariprasad@...lsio.com>
To:	netdev@...r.kernel.org
Cc:	davem@...emloft.net, leedom@...lsio.com, nirranjan@...lsio.com,
	Hariprasad Shenai <hariprasad@...lsio.com>
Subject: [PATCH net-next 0/5] cxgb4: Misc. fixes for sge 

Hi,

Increases value of MAX_IMM_TX_PKT_LEN to improve latency, fill freelist
starving threshold based on adapter type, add comments for tx flits and sge
length code and don't call t4_slow_intr_handler when we are not master PF.

This patch series has been created against net-next tree and includes patches on
cxgb4 driver

We have included all the maintainers of respective drivers. Kindly review the
change and let us know in case of any review comments.

Thanks

Hariprasad Shenai (5):
  cxgb4: Increased the value of MAX_IMM_TX_PKT_LEN from 128 to 256 bytes
  cxgb4: Freelist starving threshold varies from adapter to adapter
  cxgb4: Use device node in page allocation
  cxgb4: Add comment for calculate tx flits and sge length code
  cxgb4: Don't call t4_slow_intr_handler when we're not the Master PF

 drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c |  3 +-
 drivers/net/ethernet/chelsio/cxgb4/sge.c        | 76 +++++++++++++++++++------
 2 files changed, 62 insertions(+), 17 deletions(-)

-- 
2.3.4

--
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