All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helia Correia <helia.correia@linux.intel.com>
To: Dave Jones <davej@redhat.com>
Cc: trinity@vger.kernel.org
Subject: Re: splice syscall runs endlessly, usage problem?
Date: Tue, 03 Sep 2013 18:51:12 +0200	[thread overview]
Message-ID: <52261380.7080508@linux.intel.com> (raw)
In-Reply-To: <20130903163851.GA7397@redhat.com>

On 09/03/2013 06:38 PM, Dave Jones wrote:
> On Tue, Sep 03, 2013 at 10:48:42AM +0200, Helia Correia wrote:
>   > Hi,
>   >
>   > I am getting to know how to use Trinity, and my last attempt was to run
>   > below command (on a Fedora 17 64 bits distribution):
>   > trinity -c splice -C1 -D
>   >
>   > My problem is that this command doesn't stop running by itself (started
>   > yesterday, was still running this morning so I interrupted it), and I
>   > don't understand why but guess this is not an expected behavior, am I
>   > right? What should I do to have it run normally (I mean, start and end
>   > up gracefully)?
>   >
>   > Maybe I overlooked something but seems I couldn't find any documentation
>   > as regards to this aspect, as well as how much time it nearly takes to
>   > have Trinity run entirely, so any pointers would be highly appreciated.
>
> It will run indefinitly unless you pass -N<number> (or unless it hits a kernel
> bug that taints the kernel).
>
> 	Dave
>
>
Hi Dave,

Thanks for your input, I will try that (and indeed, -N is mentioned in 
Trinity usage, my bad :)

Best regards,
Helia

      reply	other threads:[~2013-09-03 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  8:48 splice syscall runs endlessly, usage problem? Helia Correia
2013-09-03 16:38 ` Dave Jones
2013-09-03 16:51   ` Helia Correia [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=52261380.7080508@linux.intel.com \
    --to=helia.correia@linux.intel.com \
    --cc=davej@redhat.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.