[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v1 07/16] io: add abstract QIOChannel classes
From: |
Daniel P. Berrange |
Subject: |
Re: [Qemu-devel] [PATCH v1 07/16] io: add abstract QIOChannel classes |
Date: |
Tue, 22 Sep 2015 13:24:52 +0100 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Tue, Sep 22, 2015 at 02:19:27PM +0200, Paolo Bonzini wrote:
>
>
> On 18/09/2015 15:19, Daniel P. Berrange wrote:
> > + QIO_CHANNEL_FEATURE_FD_PASS = (1 << 0),
> > + QIO_CHANNEL_FEATURE_SHUTDOWN = (1 << 1),
> > + QIO_CHANNEL_FEATURE_DELAY = (1 << 2),
> > + QIO_CHANNEL_FEATURE_CORK = (1 << 3),
>
> TCP_NODELAY and TCP_CORK are just hints; I think it is okay to just
> ignore them if not supported. You obviously disagree, so the question
> is why? :)
Well I was just trying not to second guess what future uses we might
have of the QIOChannel API, so I went for the approach of providing a
way to probe any optional features upfront. Code doesn't have to use
this if it doesn't want to - it can just ignore errors from the API
call later.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
[Qemu-devel] [PATCH v1 10/16] io: add QIOTask class for async operations, Daniel P. Berrange, 2015/09/18
[Qemu-devel] [PATCH v1 16/16] io: add QIOChannelBuffer class, Daniel P. Berrange, 2015/09/18
[Qemu-devel] [PATCH v1 08/16] io: add helper module for creating watches on FDs, Daniel P. Berrange, 2015/09/18
[Qemu-devel] [PATCH v1 11/16] io: add QIOChannelSocket class, Daniel P. Berrange, 2015/09/18
[Qemu-devel] [PATCH v1 04/16] ui: convert VNC startup code to use SocketAddress, Daniel P. Berrange, 2015/09/18
[Qemu-devel] [PATCH v1 06/16] coroutine: move into libqemuutil.a library, Daniel P. Berrange, 2015/09/18