From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, willemb@google.com
Subject: Re: [PATCH net-next] net: add scheduling point in recvmmsg/sendmmsg
Date: Sun, 10 Jan 2016 22:59:37 -0500 (EST) [thread overview]
Message-ID: <20160110.225937.1492225545440302532.davem@davemloft.net> (raw)
In-Reply-To: <1452271040.8255.226.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 08 Jan 2016 08:37:20 -0800
> From: Eric Dumazet <edumazet@google.com>
>
> Applications often have to reduce number of datagrams
> they receive or send per system call to avoid starvation problems.
>
> Really the kernel should take care of this by using cond_resched(),
> so that applications can experiment bigger batch sizes.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Seems reasonable, applied, thanks Eric.
prev parent reply other threads:[~2016-01-11 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 16:37 [PATCH net-next] net: add scheduling point in recvmmsg/sendmmsg Eric Dumazet
2016-01-11 3:59 ` David Miller [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=20160110.225937.1492225545440302532.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@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).