From: Simon Horman <horms@verge.net.au>
To: Sven Wegener <sven.wegener@stealer.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] ipvs: Cleanup sync daemon code
Date: Sun, 10 Feb 2008 10:27:12 +0900 [thread overview]
Message-ID: <20080210012710.GC3589@verge.net.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0802100029150.15729@titan.stealer.net>
On Sun, Feb 10, 2008 at 12:38:11AM +0100, Sven Wegener wrote:
> Hi all,
>
> I'd like to get your feedback on this:
>
> - Use kthread_run instead of doing a double-fork via kernel_thread()
>
> - Return proper error codes to user-space on failures
>
> Currently ipvsadm --start-daemon with an invalid --mcast-interface will
> silently suceed. With these changes we get an appropriate "No such
> device" error.
>
> - Use wait queues for both master and backup thread
>
> Instead of doing an endless loop with sleeping for one second, we now use
> wait queues. The master sync daemon has its own wait queue and gets woken
> up when we have enough data to sent and also at a regular interval. The
> backup sync daemon sits on the wait queue of the mcast socket and gets
> woken up as soon as we have data to process.
Hi Sven,
This looks good to me, assuming that its tested and works.
A few minor things:
In sb_queue_tail() master loop is woken up if
the ip_vs_sync_count reaches 10, which seems a bit arbitary.
Perhaps its just my mail reader, but the patch seemed a bit screwy when
I saved it to a file. I this fixed the problem I was seeing using s/^ / /
Unfortuantely/Fortunately I am about to leave for a few days skiing,
so if I am quiet you will know why.
Acked-by: Simon Horman <horms@verge.net.au>
--
Horms
next prev parent reply other threads:[~2008-02-10 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 23:38 [RFC] ipvs: Cleanup sync daemon code Sven Wegener
2008-02-10 1:27 ` Simon Horman [this message]
2008-02-10 4:59 ` Christoph Hellwig
2008-02-10 11:51 ` Sven Wegener
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=20080210012710.GC3589@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sven.wegener@stealer.net \
/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;
as well as URLs for NNTP newsgroup(s).