summaryrefslogtreecommitdiffstats
path: root/lib/buffer.c
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2017-10-11 15:06:02 +0200
committerDonald Sharp <sharpd@cumulusnetworks.com>2017-10-24 00:09:23 +0200
commitbf2394f08bdc91a6cbd3784a1bfa3af3247bb06f (patch)
treea4e2bb9af7813c68b5b74c0eee34522a98821389 /lib/buffer.c
parentzebra: Add a function handler for zserv commands (diff)
downloadfrr-bf2394f08bdc91a6cbd3784a1bfa3af3247bb06f.tar.xz
frr-bf2394f08bdc91a6cbd3784a1bfa3af3247bb06f.zip
lib: Cleanup some missed reformat
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'lib/buffer.c')
-rw-r--r--lib/buffer.c14
1 files changed, 8 insertions, 6 deletions
diff --git a/lib/buffer.c b/lib/buffer.c
index a7c4fe4f2..191fbf875 100644
--- a/lib/buffer.c
+++ b/lib/buffer.c
@@ -482,12 +482,14 @@ buffer_status_t buffer_write(struct buffer *b, int fd, const void *p,
ssize_t nbytes;
#if 0
- /* Should we attempt to drain any previously buffered data? This could help
- reduce latency in pushing out the data if we are stuck in a long-running
- thread that is preventing the main select loop from calling the flush
- thread... */
- if (b->head && (buffer_flush_available(b, fd) == BUFFER_ERROR))
- return BUFFER_ERROR;
+ /*
+ * Should we attempt to drain any previously buffered data?
+ * This could help reduce latency in pushing out the data if
+ * we are stuck in a long-running thread that is preventing
+ * the main select loop from calling the flush thread...
+ */
+ if (b->head && (buffer_flush_available(b, fd) == BUFFER_ERROR))
+ return BUFFER_ERROR;
#endif
if (b->head)
/* Buffer is not empty, so do not attempt to write the new data.