Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Seebs <seebs@seebs.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] pseudo: Add fastop reply fix
Date: Fri, 22 Sep 2017 11:52:04 -0500	[thread overview]
Message-ID: <20170922115204.37ef6f2c@seebsdell> (raw)
In-Reply-To: <1506098477-5444-2-git-send-email-richard.purdie@linuxfoundation.org>

On Fri, 22 Sep 2017 17:41:17 +0100
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:

> This changes the pseudo FASTOP functionality so that a reply to the
> operation is required. This means we then cannot lose data if a
> connection is closed. This in turn stops corruption if we run out of
> file handles and have to close connections.
> 
> This tweaks the connection closure patch to update the comment there
> which is now outdated.
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

This looks reasonable to me. I did some testing with a very similar
patch and concluded that, while it slowed performance slightly, it
didn't slow it nearly as much as the pre-fastop behavior did.

-s


  reply	other threads:[~2017-09-22 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 16:41 [PATCH 1/2] staging: Reduce verbosity of log messages Richard Purdie
2017-09-22 16:41 ` [PATCH 2/2] pseudo: Add fastop reply fix Richard Purdie
2017-09-22 16:52   ` Seebs [this message]
2017-09-22 17:12     ` Alexander Kanavin
2017-09-22 19:19       ` Otavio Salvador
2017-09-22 17:00 ` ✗ patchtest: failure for "staging: Reduce verbosity of l..." and 1 more Patchwork

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=20170922115204.37ef6f2c@seebsdell \
    --to=seebs@seebs.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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