From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Yishai Hadas <yishaih-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
noaos-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH rdma-core 1/2] verbs: Report the device's PCI write end paddding capability
Date: Wed, 15 Nov 2017 08:15:18 -0700 [thread overview]
Message-ID: <20171115151518.GM25894@ziepe.ca> (raw)
In-Reply-To: <915b8140-2f83-1bc2-3334-b2454f4abb33-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On Wed, Nov 15, 2017 at 03:10:30PM +0200, Yishai Hadas wrote:
> The man page was updated with a detailed description on the above
> capability, see PR:
> https://github.com/linux-rdma/rdma-core/pull/250
Yah, that is nicer
Here is some copy-editing:
Extended device capability flags (device_cap_flags_ex):
.br
.TP 7
IBV_DEVICE_PCI_WRITE_END_PADDING
Indicates the device has support for padding PCI writes to a full cache line.
Padding packets to full cache lines reduces the amount of traffic required at
the memory controller at the expense of creating more traffic on the PCI-E
port.
Workloads that have a high CPU memory load and low PCI-E utilization will
benefit from this feature, while workloads that have a high PCI-E utilization
and small packets will be harmed.
For instance, with a 128 byte cache line size, the transfer of any packets
less than 128 bytes will require a full 128 transfer on PCI, pontentially
doubling the required PCI-E bandwith.
This feature can be enabled on a QP or WQ basis via the
IBV_QP_CREATE_PCI_WRITE_END_PADDING or IBV_WQ_FLAGS_PCI_WRITE_END_PADDING
flags.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-15 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 13:47 [PATCH rdma-core 0/2] PCI write end padding Yishai Hadas
[not found] ` <1510667228-18579-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-14 13:47 ` [PATCH rdma-core 1/2] verbs: Report the device's PCI write end paddding capability Yishai Hadas
[not found] ` <1510667228-18579-2-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-14 20:30 ` Jason Gunthorpe
2017-11-14 20:33 ` Jason Gunthorpe
[not found] ` <20171114203344.GS4263-uk2M96/98Pc@public.gmane.org>
2017-11-15 13:10 ` Yishai Hadas
[not found] ` <915b8140-2f83-1bc2-3334-b2454f4abb33-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-11-15 15:15 ` Jason Gunthorpe [this message]
[not found] ` <20171115151518.GM25894-uk2M96/98Pc@public.gmane.org>
2017-11-15 16:18 ` Yishai Hadas
2017-11-14 13:47 ` [PATCH rdma-core 2/2] verbs: Enable QP and WQ creation with PCI write end padding option Yishai Hadas
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=20171115151518.GM25894@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=noaos-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=yishaih-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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