From: Dave Jones <davej@redhat.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH 0/4] Teach trinity to not use some sockets family
Date: Thu, 31 Oct 2013 15:49:43 -0400 [thread overview]
Message-ID: <20131031194943.GA8696@redhat.com> (raw)
In-Reply-To: <CAM5jBj5dvv1HP6ffRnP+b5sQkd0mP3nDcEU-N6+pYvaZ6b3epw@mail.gmail.com>
On Fri, Oct 25, 2013 at 11:48:58AM +0400, Cyrill Gorcunov wrote:
> On Fri, Oct 25, 2013 at 1:39 AM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> > When I've been running trinity on testing machine admins were
> > not that happy about traffic generated by trinity (especially
> > ones created with packet socket). So here is an attempt to teach
> > trinity to use say only some set of sockets if needed with help
> > of --fds option.
> >
> > Please take a look, thanks.
>
> Drop the serice please, it'll be reworked.
I'm about to apply your later series, but I noticed that that one
instead of the --fds patch, has the -E change.
Do you still plan on submitting the --fds change later?
The reason I ask is that it if we're doing --fds, then it might at some point
mean we can deprecate (and then remove) use of -P in favor of it, so adding an
inverse (-E) seems odd.
Dave
next prev parent reply other threads:[~2013-10-31 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 21:39 [PATCH 0/4] Teach trinity to not use some sockets family Cyrill Gorcunov
2013-10-24 21:39 ` [PATCH 1/4] make: Add cscope target Cyrill Gorcunov
2013-10-24 21:39 ` [PATCH 2/4] log: Add BUG_ON helper Cyrill Gorcunov
2013-10-24 21:39 ` [PATCH 3/4] params: Add parsing of -f|--fds option Cyrill Gorcunov
2013-10-24 21:39 ` [PATCH 4/4] sockets: Take into account socket families disabled when generating sockets Cyrill Gorcunov
2013-10-25 7:48 ` [PATCH 0/4] Teach trinity to not use some sockets family Cyrill Gorcunov
2013-10-31 19:49 ` Dave Jones [this message]
2013-10-31 20:05 ` Cyrill Gorcunov
2013-10-31 20:20 ` Dave Jones
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=20131031194943.GA8696@redhat.com \
--to=davej@redhat.com \
--cc=gorcunov@gmail.com \
--cc=trinity@vger.kernel.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.