public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: 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: Tue, 14 Nov 2017 13:30:59 -0700	[thread overview]
Message-ID: <20171114203059.GR4263@ziepe.ca> (raw)
In-Reply-To: <1510667228-18579-2-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On Tue, Nov 14, 2017 at 03:47:07PM +0200, Yishai Hadas wrote:
> From: Noa Osherovich <noaos-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> 
> There are PCIe root complex that are able to optimize their
> performance when incoming data is multiple full cache lines.
> Expose the device capability to report whether the device supports
> padding the ending of incoming packets to full cache line, such that
> the last upstream write generated by the incoming packet will be a
> full cache line.
> 
> User should consider several factors before activating this feature:
> - In case of high CPU memory load (which may cause PCI backpressure in
>   turn), if a large percent of the writes are partial cache line, this
>   feature should be checked as an optional solution.
> - This feature might reduce performance if most packets are between
>   one and two cache lines and PCIe throughput has reached its maximum
>   capacity. E.g. 65B packet from the network port will lead to 128B
>   write on PCIe, which may cause trafiic on PCIe to reach high
>   throughput.

This commit message would make a far better man page revision than
what was provided :(

Jason
--
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

  parent reply	other threads:[~2017-11-14 20:30 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 [this message]
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
     [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=20171114203059.GR4263@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-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