From: Arjan van de Ven <arjan@infradead.org>
To: Steve Wise <swise@opengridcomputing.com>
Cc: rdreier@cisco.com, mshefty@ichips.intel.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH v3 1/7] AMSO1100 Low Level Driver.
Date: Tue, 20 Jun 2006 22:43:46 +0200 [thread overview]
Message-ID: <1150836226.2891.231.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060620203055.31536.15131.stgit@stevo-desktop>
On Tue, 2006-06-20 at 15:30 -0500, Steve Wise wrote:
> +/*
> + * Allocate TX ring elements and chain them together.
> + * One-to-one association of adapter descriptors with ring elements.
> + */
> +static int c2_tx_ring_alloc(struct c2_ring *tx_ring, void *vaddr,
> + dma_addr_t base, void __iomem * mmio_txp_ring)
> +{
> + struct c2_tx_desc *tx_desc;
> + struct c2_txp_desc __iomem *txp_desc;
> + struct c2_element *elem;
> + int i;
> +
> + tx_ring->start = kmalloc(sizeof(*elem) * tx_ring->count, GFP_KERNEL);
I would think this needs a dma_alloc_coherent() rather than a kmalloc...
> +
> +/* Free all buffers in RX ring, assumes receiver stopped */
> +static void c2_rx_clean(struct c2_port *c2_port)
> +{
> + struct c2_dev *c2dev = c2_port->c2dev;
> + struct c2_ring *rx_ring = &c2_port->rx_ring;
> + struct c2_element *elem;
> + struct c2_rx_desc *rx_desc;
> +
> + elem = rx_ring->start;
> + do {
> + rx_desc = elem->ht_desc;
> + rx_desc->len = 0;
> +
> + __raw_writew(0, elem->hw_desc + C2_RXP_STATUS);
> + __raw_writew(0, elem->hw_desc + C2_RXP_COUNT);
> + __raw_writew(0, elem->hw_desc + C2_RXP_LEN);
you seem to be a fan of the __raw_write() functions... any reason why?
__raw_ is not a magic "go faster" prefix....
Also on a related note, have you checked the driver for the needed PCI
posting flushes?
> +
> + /* Disable IRQs by clearing the interrupt mask */
> + writel(1, c2dev->regs + C2_IDIS);
> + writel(0, c2dev->regs + C2_NIMR0);
like here...
> +
> + elem = tx_ring->to_use;
> + elem->skb = skb;
> + elem->mapaddr = mapaddr;
> + elem->maplen = maplen;
> +
> + /* Tell HW to xmit */
> + __raw_writeq(cpu_to_be64(mapaddr), elem->hw_desc + C2_TXP_ADDR);
> + __raw_writew(cpu_to_be16(maplen), elem->hw_desc + C2_TXP_LEN);
> + __raw_writew(cpu_to_be16(TXP_HTXD_READY), elem->hw_desc + C2_TXP_FLAGS);
or here
> +static int c2_change_mtu(struct net_device *netdev, int new_mtu)
> +{
> + int ret = 0;
> +
> + if (new_mtu < ETH_ZLEN || new_mtu > ETH_JUMBO_MTU)
> + return -EINVAL;
> +
> + netdev->mtu = new_mtu;
> +
> + if (netif_running(netdev)) {
> + c2_down(netdev);
> +
> + c2_up(netdev);
> + }
this looks odd...
next prev parent reply other threads:[~2006-06-20 20:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 20:30 [PATCH v3 0/7][RFC] Ammasso 1100 iWARP Driver Steve Wise
2006-06-20 20:30 ` [PATCH v3 1/7] AMSO1100 Low Level Driver Steve Wise
2006-06-20 20:43 ` Arjan van de Ven [this message]
2006-06-21 16:32 ` Steve Wise
2006-06-21 17:13 ` Arjan van de Ven
2006-06-21 18:47 ` Steve Wise
2006-06-21 17:37 ` [openib-general] " Grant Grundler
2006-06-23 13:44 ` Steve Wise
2006-06-23 13:48 ` Arjan van de Ven
2006-06-23 13:56 ` Steve Wise
2006-06-23 14:04 ` Arjan van de Ven
2006-06-23 17:14 ` [openib-general] " Grant Grundler
2006-06-20 20:31 ` [PATCH v3 3/7] AMSO1100 OpenFabrics Provider Steve Wise
2006-06-20 20:31 ` [PATCH v3 4/7] AMSO1100 Memory Management Steve Wise
2006-06-20 20:31 ` [PATCH v3 5/7] AMSO1100 Message Queues Steve Wise
2006-06-20 20:31 ` [PATCH v3 6/7] AMSO1100: Privileged Verbs Queues Steve Wise
2006-06-20 20:31 ` [PATCH v3 7/7] AMSO1100 Makefiles and Kconfig changes Steve Wise
2006-06-20 21:00 ` [PATCH v3 2/7] AMSO1100 WR / Event Definitions Steve Wise
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=1150836226.2891.231.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshefty@ichips.intel.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
--cc=swise@opengridcomputing.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