public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: rdreier@cisco.com, linux-kernel@vger.kernel.org,
	openib-general@openib.org
Subject: Re: [PATCH 12 of 16] ipath - infiniband RC protocol support
Date: Thu, 30 Mar 2006 22:36:33 +0200	[thread overview]
Message-ID: <20060330203633.GA29023@elf.ucw.cz> (raw)
In-Reply-To: <2fe2c58d0de99a067ae1.1143674615@chalcedony.internal.keyresearch.com>

Hi!

> This is an implementation of the Infiniband RC ("reliable connection")
> protocol.

> +/* cut down ridiculously long IB macro names */
> +#define OP(x) IB_OPCODE_RC_##x

Heh... what about fixing those names in the first place?

> +	/* GRH header size in 32-bit words. */
> +	qp->s_hdrwords += 10;
> +	qp->s_hdr.u.l.grh.version_tclass_flow =
> +		cpu_to_be32((6 << 28) |
> +			    (grh->traffic_class << 20) |
> +			    grh->flow_label);
> +	qp->s_hdr.u.l.grh.paylen =
> +		cpu_to_be16(((qp->s_hdrwords - 12) + nwords +
> +			     SIZE_OF_CRC) << 2);
> +	/* next_hdr is defined by C8-7 in ch. 8.4.1 */
> +	qp->s_hdr.u.l.grh.next_hdr = 0x1B;
> +	qp->s_hdr.u.l.grh.hop_limit = grh->hop_limit;
> +	/* The SGID is 32-bit aligned. */
> +	qp->s_hdr.u.l.grh.sgid.global.subnet_prefix = dev->gid_prefix;
> +	qp->s_hdr.u.l.grh.sgid.global.interface_id =
> +		ipath_layer_get_guid(dev->dd);
> +	qp->s_hdr.u.l.grh.dgid = grh->dgid;

Don't know about you, but it looks like perl code to
me. qp->s_hdr.u.l.grh.next_hdr ?

> +	/* Check for a constructed packet to be sent. */
> +	if (qp->s_hdrwords != 0) {
> +		/*
> +		 * If no PIO bufs are available, return.  An interrupt will
> +		 * call ipath_ib_piobufavail() when one is available.
> +		 */
> +		_VERBS_INFO("h %u %p\n", qp->s_hdrwords, &qp->s_hdr);
> +		_VERBS_INFO("d %u %p %u %p %u %u %u %u\n",  qp->s_cur_size,

Info on verbs, or verbose info? Why does it start with _ ? What is
wrong with printk?
								Pavel
-- 
Picture of sleeping (Linux) penguin wanted...

  reply	other threads:[~2006-03-30 20:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 23:23 [PATCH 0 of 16] ipath - driver submission for 2.6.17 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 1 of 16] ipath - core device driver Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 2 of 16] ipath - core driver header files Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 3 of 16] ipath - support for HyperTransport devices Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 4 of 16] ipath - support for PCI Express devices Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 5 of 16] ipath - chip initialisation code, and diag support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 6 of 16] ipath - misc driver support code Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 7 of 16] ipath - sysfs and ipathfs support for core driver Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 8 of 16] ipath - support for userspace apps using " Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 9 of 16] ipath - layering interfaces used by higher-level driver code Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 10 of 16] ipath - infiniband header files Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 11 of 16] ipath - infiniband UC and UD protocol support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 12 of 16] ipath - infiniband RC " Bryan O'Sullivan
2006-03-30 20:36   ` Pavel Machek [this message]
2006-03-29 23:23 ` [PATCH 13 of 16] ipath - misc infiniband code, part 1 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 14 of 16] ipath - misc infiniband code, part 2 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 15 of 16] ipath - infiniband verbs support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 16 of 16] ipath - kbuild infrastructure Bryan O'Sullivan
2006-03-30 21:06   ` Roland Dreier
2006-03-30 21:55     ` Bryan O'Sullivan
2006-03-30 22:36       ` Roland Dreier
2006-03-31  3:53         ` Sam Ravnborg
2006-03-30 20:59 ` [PATCH 0 of 16] ipath - driver submission for 2.6.17 Roland Dreier
2006-03-30 21:54   ` Bryan O'Sullivan

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=20060330203633.GA29023@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bos@pathscale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.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