From: Doug Ledford <dledford@redhat.com>
To: Gerd Rausch <gerd.rausch@oracle.com>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com
Cc: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 0/5] net/rds: Fixes from internal Oracle repo
Date: Wed, 14 Aug 2019 11:59:03 -0400 [thread overview]
Message-ID: <be26c48a5a749a80d7c5fdb6cb92b5c9dbf6b535.camel@redhat.com> (raw)
In-Reply-To: <0b05ed75-6772-e339-11e6-1fb5714981c0@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
On Tue, 2019-08-13 at 11:20 -0700, Gerd Rausch wrote:
> This is the first set of (mostly old) patches from our internal
> repository
> in an effort to synchronize what Oracle had been using internally
> with what is shipped with the Linux kernel.
>
> Andy Grover (2):
> RDS: Re-add pf/sol access via sysctl
> rds: check for excessive looping in rds_send_xmit
>
> Chris Mason (2):
> RDS: limit the number of times we loop in rds_send_xmit
> RDS: don't use GFP_ATOMIC for sk_alloc in rds_create
>
> Gerd Rausch (1):
> net/rds: Add a few missing rds_stat_names entries
>
> net/rds/af_rds.c | 2 +-
> net/rds/ib_recv.c | 12 +++++++++++-
> net/rds/rds.h | 2 +-
> net/rds/send.c | 12 ++++++++++++
> net/rds/stats.c | 3 +++
> net/rds/sysctl.c | 21 +++++++++++++++++++++
> 6 files changed, 49 insertions(+), 3 deletions(-)
>
That first patch looks like a total bogon to me, but the remaining four
look fine.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-14 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 18:20 [PATCH net-next 0/5] net/rds: Fixes from internal Oracle repo Gerd Rausch
2019-08-14 15:59 ` 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=be26c48a5a749a80d7c5fdb6cb92b5c9dbf6b535.camel@redhat.com \
--to=dledford@redhat.com \
--cc=davem@davemloft.net \
--cc=gerd.rausch@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.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;
as well as URLs for NNTP newsgroup(s).