From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2 v4] net/macb: RX path enhancement
Date: Thu, 06 Jun 2013 16:23:58 -0700 (PDT) [thread overview]
Message-ID: <20130606.162358.506642916485125446.davem@davemloft.net> (raw)
In-Reply-To: <cover.1370418770.git.nicolas.ferre@atmel.com>
From: Nicolas Ferre <nicolas.ferre@atmel.com>
Date: Wed, 5 Jun 2013 09:57:10 +0200
> Here is the patch series for modifying the RX path in macb driver.
> This change applies on GEM variant of the Cadence IP and introduces
> function pointers to match the path to the proper adapter. The move
> to RX buffers adapted to MTU and that can be DMAed directly in SKB
> is done in two steps but can be merged in a single patch.
>
> v4: - rebased on top of net-next
> - removed the last patch of the series which needs rework
>
> v3: - rebased on top of net-next (containing recently added
> net/macb: fix ISR clear-on-write behavior only for some SoC)
> - added the ___cacheline_aligned_in_smp qualifier to napi field
> following Ben Hutchings' advice
>
> v2: - gave up the idea of using non-coherent memory for
> rx buffers
> - addition of the struct macb layout optimization
Applied to net-next but I had to fix the printf format strings
used in macb_init_rx_buffer_size().
netdev->mtu is "unsigned int" so "%u"
bp->rx_buffer_size is "size_t" so "%Zu"
otherwise we get build warnings.
next prev parent reply other threads:[~2013-06-06 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 7:57 [PATCH 0/2 v4] net/macb: RX path enhancement Nicolas Ferre
2013-06-05 7:57 ` [PATCH 1/2 v4] net/macb: increase RX buffer size for GEM Nicolas Ferre
2013-06-05 7:57 ` [PATCH 2/2 v4] net/macb: change RX path " Nicolas Ferre
2013-06-06 23:23 ` David Miller [this message]
2013-06-07 8:36 ` [PATCH 0/2 v4] net/macb: RX path enhancement Nicolas Ferre
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=20130606.162358.506642916485125446.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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).