netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: netdev@vger.kernel.org
Subject: Re: BUG: sk_backlog.len can overestimate
Date: Tue, 1 Oct 2019 13:53:09 -0700	[thread overview]
Message-ID: <f572890a-ca31-e01a-e370-c8b3e3b51f5b@gmail.com> (raw)
In-Reply-To: <CAGXJAmy7PTZOcwRz-mSiZJkEL4sJKWhkE8kisUZp8M=V1BBA3g@mail.gmail.com>



On 10/1/19 1:45 PM, John Ousterhout wrote:

> 
> But this isn't really about socket resource limits (though that is
> conflated in the implementation); it's about limiting the time spent
> in a single call to __release_sock, no?

The proxy used is memory usage, not time usage.

cond_resched() or a preemptible kernel makes anything based on time flaky,
you probably do not want to play with a time limit...




  reply	other threads:[~2019-10-01 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGXJAmwQw1ohc48NfAvMyNDpDgHGkdVO89Jo8B0j0TuMr7wLpA@mail.gmail.com>
2019-09-30 23:58 ` BUG: sk_backlog.len can overestimate John Ousterhout
2019-10-01  0:14   ` Eric Dumazet
2019-10-01 15:44     ` John Ousterhout
     [not found]     ` <CAGXJAmxmJ-Vm379N4nbjXeQCAgY9ur53wmr0HZy23dQ_t++r-Q@mail.gmail.com>
     [not found]       ` <f4520c32-3133-fb3b-034e-d492d40eb066@gmail.com>
2019-10-01 15:46         ` Fwd: " John Ousterhout
2019-10-01 15:48         ` John Ousterhout
2019-10-01 16:19           ` Eric Dumazet
2019-10-01 17:25             ` John Ousterhout
2019-10-01 18:34               ` Eric Dumazet
2019-10-01 20:45                 ` John Ousterhout
2019-10-01 20:53                   ` Eric Dumazet [this message]
2019-10-01 23:01                     ` John Ousterhout

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=f572890a-ca31-e01a-e370-c8b3e3b51f5b@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ouster@cs.stanford.edu \
    /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).