From: jamal <hadi@cyberus.ca>
To: netdev@vger.kernel.org
Cc: Andi Kleen <andi@firstfloor.org>, David Miller <davem@davemloft.net>
Subject: [RFC] IP_RECVERRC
Date: Fri, 10 Aug 2007 09:35:12 -0400 [thread overview]
Message-ID: <1186752912.5188.12.camel@localhost> (raw)
It seems there are a lot of dumbass apps (latest i have found is iperf
when analyzing batching results) out there whose performance is affected
if they dont set IP_RECVERR.
If you set that option though you end up getting all these skbs back
to the app which i see as unnecessary work if i am uninterested. I would
like to not do a recvmsg to find out what those messages are - rather
just receiving any errors back.
My proposal is to add another option which is mutually exclusive with
IP_RECVERR that allows for errors only.
Can i get a ye before i implement?
Andi, CCing you because i think you may be the person who added
IP_RECVERR (at least the first time i heard it a few years back was from
you).
cheers,
jamal
next reply other threads:[~2007-08-10 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 13:35 jamal [this message]
2007-08-10 14:02 ` [RFC] IP_RECVERRC Andi Kleen
2007-08-10 14:30 ` jamal
2007-08-10 16:26 ` Andi Kleen
2007-08-11 19:27 ` jamal
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=1186752912.5188.12.camel@localhost \
--to=hadi@cyberus.ca \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--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).