From: Jason Baron <jbaron@akamai.com>
To: David Miller <davem@davemloft.net>
Cc: edumazet@google.com, netdev@vger.kernel.org,
ncardwell@google.com, ycheng@google.com
Subject: Re: [PATCH] tcp: ensure epoll edge trigger wakeup when out of memory
Date: Tue, 19 May 2015 10:10:33 -0400 [thread overview]
Message-ID: <555B4459.806@akamai.com> (raw)
In-Reply-To: <20150519.001045.1156234709900758412.davem@davemloft.net>
On 05/19/2015 12:10 AM, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Tue, 19 May 2015 00:09:45 -0400 (EDT)
>
>> From: Jason Baron <jbaron@akamai.com>
>> Date: Fri, 15 May 2015 21:17:07 +0000 (GMT)
>>
>>> From: Jason Baron <jbaron@akamai.com>
>>>
>>> If we really can't get an skb allocated, make sure that we let
>>> userspace know. This at least gives us a chance to re-try or abort.
>>>
>>> Signed-off-by: Jason Baron <jbaron@akamai.com>
>> Applied to net-next, thanks Jason.
> Nevermind, reverted, you didn't compile let alone test this:
>
Hi David,
This was meant as: "do you think this is a good idea? If so, I will
go off and test it. I mentioned it was *not* tested in the separate
thread where we were discussing it:
http://marc.info/?l=linux-netdev&m=143172482802074&w=2
However, I didn't make that at all clear in *this* thread. And I'm
sorry for the inconvenience.
I meant to do:
+ if (unlikely(skb_queue_len(&sk->sk_write_queue) == 0 && err ==
-EAGAIN))
+ sk->sk_write_space(sk);
not:
+ if (unlikely(sk->sk_write_queue == 0 && err == -EAGAIN))
+ sk->sk_write_space(sk);
Sounds like you are ok with doing the wakeup here- so I will go
off and test that approach, and report back my findings.
Thanks,
-Jason
prev parent reply other threads:[~2015-05-19 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 21:17 [PATCH] tcp: ensure epoll edge trigger wakeup when out of memory Jason Baron
2015-05-18 2:50 ` Eric Dumazet
2015-05-19 4:09 ` David Miller
2015-05-19 4:10 ` David Miller
2015-05-19 14:10 ` Jason Baron [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=555B4459.806@akamai.com \
--to=jbaron@akamai.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).