From: Stephen Hemminger <shemminger@vyatta.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] drivers/net/tile/: on-chip network drivers for the tile architecture
Date: Wed, 3 Nov 2010 12:59:59 -0400 [thread overview]
Message-ID: <20101103125959.3231daa1@s6510> (raw)
In-Reply-To: <201011012107.oA1L7TGd031588@farm-0027.internal.tilera.com>
On Mon, 1 Nov 2010 17:00:37 -0400
Chris Metcalf <cmetcalf@tilera.com> wrote:
> This change adds the first network driver for the tile architecture,
> supporting the on-chip XGBE and GBE shims.
>
> The infrastructure is present for the TILE-Gx networking drivers (another
> three source files in the new directory) but for now the the actual
> tilegx sources are waiting on releasing hardware to initial customers.
>
> Note that arch/tile/include/hv/* are "upstream" headers from the
> Tilera hypervisor and will probably benefit less from LKML review.
>
> Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
> +typedef struct {
> + /** Byte offset of the next notify packet to be written: zero for the first
> + * packet on the queue, sizeof (netio_pkt_t) for the second packet on the
> + * queue, etc. */
> + volatile uint32_t __packet_write;
> +
> + /** Offset of the packet after the last valid packet (i.e., when any
> + * pointer is incremented to this value, it wraps back to zero). */
> + uint32_t __last_packet_plus_one;
> +}
> +__netio_packet_queue_t;
1. MUST not use volatile, see volatile-considered-harmful.txt
2. SHOULD use __u32 rather than uint32_t in kernel structures
3. MUST not introduce typedef's; use structures
4. SHOULD use proper kernel implementation
If you use scripts/checkpatch.pl it will tell you about these.
next prev parent reply other threads:[~2010-11-03 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 21:00 [PATCH] drivers/net/tile/: on-chip network drivers for the tile architecture Chris Metcalf
2010-11-03 16:59 ` Stephen Hemminger [this message]
2010-11-03 17:37 ` Chris Metcalf
2010-11-03 17:50 ` Eric Dumazet
2010-11-03 19:39 ` Chris Metcalf
2010-11-03 20:31 ` Eric Dumazet
2010-11-03 21:04 ` Chris Metcalf
2010-11-01 21:00 ` [PATCH v2] " Chris Metcalf
2010-11-14 7:52 ` Sam Ravnborg
2010-11-15 18:22 ` David Miller
2010-11-15 19:01 ` Chris Metcalf
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=20101103125959.3231daa1@s6510 \
--to=shemminger@vyatta.com \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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