netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jbaron@akamai.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH] tcp: set SOCK_NOSPACE under memory presure
Date: Thu, 30 Apr 2015 11:44:38 -0400 (EDT)	[thread overview]
Message-ID: <20150430.114438.1344047101033865261.davem@davemloft.net> (raw)
In-Reply-To: <55423D69.7000907@akamai.com>

From: Jason Baron <jbaron@akamai.com>
Date: Thu, 30 Apr 2015 10:34:17 -0400

> Just curious if anybody had any further reaction on this issue.
> I think making the epoll edge trigger case, as least match what
> we are seeing for poll()/select()/epoll() level trigger seems
> reasonable here.

It's in my inbox and looking into this is on my TODO list.

I simply lack the time right now and you will need to be
patient.

  reply	other threads:[~2015-04-30 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 20:05 [PATCH] tcp: set SOCK_NOSPACE under memory presure Jason Baron
2015-04-21 21:33 ` David Miller
2015-04-22 14:25   ` Jason Baron
2015-04-30 14:34     ` Jason Baron
2015-04-30 15:44       ` David Miller [this message]
2015-05-04 23:12       ` David Miller

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=20150430.114438.1344047101033865261.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jbaron@akamai.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).