From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-next v1 0/3] IPoIB TX NAPI
Date: Wed, 25 Oct 2017 13:38:51 -0400 [thread overview]
Message-ID: <1508953131.3325.37.camel@redhat.com> (raw)
In-Reply-To: <20171019045644.5816-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Thu, 2017-10-19 at 07:56 +0300, Leon Romanovsky wrote:
> Changelog from v0:
> * Rebase to latest for-next, commit 894b82c427d0 ("Merge branch
> 'timer_setup' into for-next")
>
> ----
> From Erez Shitrit <erezsh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> ----
>
> It is very common in modern network devices to use NAPI in RX and TX,
> in the UD/TX flows IPoIB uses a polling mechanism (not as it does in
> the CM mode).
>
> Except of the motivation to use the same mechanism for IPoIB as for
> netdevices, there are number of issues in current polling mechanism:
> * SKBs that are kept longer than they should be and there are
> applications
> that warn about that (some firewalls for example).
> * Statistics that are not updated to the real value. It blocks
> support
> for time synchronization protocols over the IPoIB protocol, like
> PTP
> and so on.
> * The TX in CM mode already uses NAPI, there is no reason to keep
> two
> different ways for TX one for UD and one for the CM.
>
> The patches are available in the git repository at:
> git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git
> tags/rdma-next-2017-10-19
Thanks, applied (in lieu of the original patch set that I already
replied to).
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
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
prev parent reply other threads:[~2017-10-25 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 4:56 [PATCH rdma-next v1 0/3] IPoIB TX NAPI Leon Romanovsky
[not found] ` <20171019045644.5816-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-10-19 4:56 ` [PATCH rdma-next v1 1/3] IB/ipoib: Get rid of the tx_outstanding variable in all modes Leon Romanovsky
2017-10-19 4:56 ` [PATCH rdma-next v1 2/3] IB/ipoib: Use NAPI in UD/TX flows Leon Romanovsky
2017-10-19 4:56 ` [PATCH rdma-next v1 3/3] IB/ipoib: Change number of TX wqe to 64 Leon Romanovsky
2017-10-25 17:38 ` Doug Ledford [this message]
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=1508953131.3325.37.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.