All of lore.kernel.org
 help / color / mirror / Atom feed
From: 'Arnaldo Carvalho de Melo' <acme@kernel.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "David Miller" <davem@davemloft.net>,
	"Linux Networking Development Mailing List"
	<netdev@vger.kernel.org>,
	"Caitlin Bestler" <caitlin.bestler@gmail.com>,
	"Chris Friesen" <chris.friesen@windriver.com>,
	"Elie De Brauwer" <eliedebrauwer@gmail.com>,
	"Michael Kerrisk" <mtk.manpages@gmail.com>,
	"Neil Horman" <nhorman@tuxdriver.com>,
	"Ondřej Bílka" <neleai@seznam.cz>,
	"Paul Moore" <paul@paul-moore.com>,
	"Rémi Denis-Courmont" <remi@remlab.net>,
	"Steven Whitehouse" <steve@chygwyn.com>
Subject: Re: [PATCH/RFC] net: Don't save mid batch datagram processing error for next recvmmsg call
Date: Tue, 22 Jul 2014 10:24:10 -0300	[thread overview]
Message-ID: <20140722132410.GD20303@kernel.org> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1727AECC@AcuExch.aculab.com>

Em Tue, Jul 22, 2014 at 08:33:27AM +0000, David Laight escreveu:
> From: Arnaldo Carvalho de Melo 
> > 	I think this addresses the problems reported by David Laight and
> > others, where errors saved on a per socket area could be delivered to a
> > different thread, so I just followed David Laight's suggestion and
> > stopped saving it, we'll return it only if it happens for the first
> > datagram, else we return less entries than asked for.

> > 	Steven, IIRC you was the one that suggested using this
> > mechanism, no? Do you have anything against this move?
 
> +	return datagrams ?: err;
 
> Inline patches, don't attach them.

Oh well, ok, will do next time.
 
> Don't use non-C constructs.

We use it in many places, one could say the kernel isn't written in C
anyway:

[acme@zoo linux]$ find . -name "*.[ch]" | xargs grep '?:' | cut -d'/' -f -2 | sort | uniq -c | sort -nr
    189 ./drivers
     45 ./arch
     33 ./crypto
     30 ./fs
     25 ./net
     23 ./kernel
     22 ./tools
      9 ./sound
      8 ./include
      5 ./security
      5 ./mm
      3 ./block
      2 ./lib
      1 ./scripts
      1 ./ipc
[acme@zoo linux]$

Other than that, are you ok with the change?

- Arnaldo

      reply	other threads:[~2014-07-22 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 19:30 [PATCH/RFC] net: Don't save mid batch datagram processing error for next recvmmsg call Arnaldo Carvalho de Melo
2014-07-22  4:17 ` David Miller
2014-07-22  8:33 ` David Laight
2014-07-22 13:24   ` 'Arnaldo Carvalho de Melo' [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=20140722132410.GD20303@kernel.org \
    --to=acme@kernel.org \
    --cc=David.Laight@ACULAB.COM \
    --cc=caitlin.bestler@gmail.com \
    --cc=chris.friesen@windriver.com \
    --cc=davem@davemloft.net \
    --cc=eliedebrauwer@gmail.com \
    --cc=mtk.manpages@gmail.com \
    --cc=neleai@seznam.cz \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=paul@paul-moore.com \
    --cc=remi@remlab.net \
    --cc=steve@chygwyn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.