From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, santosh.shilimkar@oracle.com,
rds-devel@oss.oracle.com
Subject: Re: [PATCH net-next] rds: do not call ->conn_alloc with GFP_KERNEL
Date: Tue, 13 Feb 2018 12:07:47 -0500 [thread overview]
Message-ID: <20180213170747.GL29321@oracle.com> (raw)
In-Reply-To: <20180213.120421.840213231623736121.davem@davemloft.net>
On (02/13/18 12:04), David Miller wrote:
>
> Let's not over-engineer this. For one thing, whatever allocation bits
> came down from the callers, we are going to lose here.
Ok, I was wondering how much of the sk_allocation we want to keep in
the future, so I did this admittedly weird thing. I'll change it
to the obvious and submit v3.
--Sowmini
prev parent reply other threads:[~2018-02-13 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 23:30 [PATCH net-next] rds: do not call ->conn_alloc with GFP_KERNEL Sowmini Varadhan
2018-02-13 17:04 ` David Miller
2018-02-13 17:07 ` Sowmini Varadhan [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=20180213170747.GL29321@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--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).