All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Molton <ian.molton@collabora.co.uk>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/5] socket: Add a reconnect option.
Date: Tue, 02 Feb 2010 10:23:09 +0000	[thread overview]
Message-ID: <4B67FD0D.1070900@collabora.co.uk> (raw)
In-Reply-To: <4B675BBA.2080907@codemonkey.ws>

Anthony Liguori wrote:

> I'm all for doing things incrementally but there has to be a big picture
> that the incremental bit fits into otherwise you end up with a bunch of
> random features that don't work together well.

Well, if you just add stuff without ever changing anything that went
before, of course.

> Honestly, I'd strongly suggest splitting the reconnect logic out of the
> series when resubmitting.

IMO the RNG stuff is worthless without the reconnect logic. You cant
have a machine in a production environment that just stops getting
entropy forever when you (say) restart the EGD, perhaps during a package
update. Or when someone unplugs the entropy source temporarily or
something like that.

>  I think it's just too hacky with too weak of
> a justification.  If you really want this functionality, we can discuss
> the right approach for doing it but it's gotta be done in a way that's
> not introducing a one-off case just for the random number generator.

I dont think its a case of 'really want' as much as 'its completely
essential' :-)

I still think that unless there are any other use cases, theres not much
to discuss - The code is already generic to some degree - it notifies
users, and its got a configurable delay. What else do we need? I
implemented it generically rather than stuff it into the virtio-rng
driver *because* I didnt think a dedicated version of it was the right
way to go, but without some other use cases, I cant see what good there
is in bikeshedding over this?

-Ian

      reply	other threads:[~2010-02-02 10:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 13:34 [Qemu-devel] [PATCH] resend: socket reconnect and virtio-rng support Ian Molton
2010-02-01 13:34 ` [Qemu-devel] [PATCH 1/5] socket: Rationalise function declarations Ian Molton
2010-02-01 13:34   ` [Qemu-devel] [PATCH 2/5] socket: Add a reconnect option Ian Molton
2010-02-01 13:34     ` [Qemu-devel] [PATCH 3/5] Add SIZE type to qdev properties Ian Molton
2010-02-01 13:34       ` [Qemu-devel] [PATCH 4/5] virtio: Add virtio-rng driver Ian Molton
2010-02-01 13:34         ` [Qemu-devel] [PATCH 5/5] Build fix (missing header) Ian Molton
2010-02-01 15:31         ` [Qemu-devel] [PATCH 4/5] virtio: Add virtio-rng driver Anthony Liguori
2010-02-01 16:03           ` Gerd Hoffmann
2010-02-01 16:50             ` Anthony Liguori
2010-02-01 22:41             ` Ian Molton
2010-02-01 22:48           ` Ian Molton
2010-02-09 10:50             ` Ian Molton
2010-02-01 15:25     ` [Qemu-devel] [PATCH 2/5] socket: Add a reconnect option Anthony Liguori
2010-02-01 16:12       ` Luiz Capitulino
2010-02-01 16:49         ` Anthony Liguori
2010-02-01 22:44       ` Ian Molton
2010-02-01 22:54         ` Anthony Liguori
2010-02-02 10:23           ` Ian Molton [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=4B67FD0D.1070900@collabora.co.uk \
    --to=ian.molton@collabora.co.uk \
    --cc=anthony@codemonkey.ws \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.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 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.