public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] [RFC] Testcase for recvmmsg(), a syscall for	batching	recvmsg() calls
Date: Tue, 18 May 2010 01:36:00 +0530	[thread overview]
Message-ID: <1274126761.5106.14.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <20100512212031.GI30926@ghostprotocols.net>

On Wed, 2010-05-12 at 18:20 -0300, Arnaldo Carvalho de Melo wrote: 
> Em Wed, May 12, 2010 at 11:10:23PM +0530, Subrata Modak escreveu:
> > Hello Arnaldo,
> > 
> > Your code in 2.6.33 kernel introduced a new system call called
> > recvmmsg(), a syscall for batching recvmsg() calls. Would you like to
> > share the set of test cases you used to test this new code with the LTP
> > community ?
> 
> Forgive me my ignorance about the current state of the LTP
> infrastructure, but does it support requiring multiple clients and a
> server to test networking calls? Or is everything done over loopback?

Sorry for the very late reply. No, we also have something called LTP
network tests, which require a separate server and client, and is
designed to burn the network wires and not the loopback interface.

Your test seems interesting. I will like to integrate the code later in
our networking tests when i find time. If there is a more active
volunteer, he is welcome to do it before me ;-)

Regards--
Subrata

> 
> The tests I did were basically:
> 
> On several client machines:
> 
> use netcat to continuously send datagrams to a destination machine on
> a specified port (5001, the ttcp one is used as a default)
> 
> On the server:
> 
> run the attached testcase, then I was basically visually looking that
> every batch received packets from multiple clients.
> 
> I can envision a test where from the machine chosen to be the server a
> script like:
> 
> #!/bin/sh
> 
> ./recvmmsg &
> 
> for client in $CLIENTS ; do
> 	ssh client ./run-netcat-script.sh $SERVER
> done
> 
> # --- end ---
> 
> The attached recvmmsg would somehow get the list of clients, check that
> they are the sendeds in datagrams in the same batch, and if so, woud
> emit a PASSED as output.
> 
> Another question about the LTP infrastructure: Do it already supports
> collecting measurements in databases, associated to the kernel, libc,
> etc, versions, so that this can be used to generate plottings of metrics
> over time/kernel versions?
> 
> - Arnaldo


------------------------------------------------------------------------------

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2010-05-17 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 17:40 [LTP] [RFC] Testcase for recvmmsg(), a syscall for batching recvmsg() calls Subrata Modak
     [not found] ` <20100512212031.GI30926@ghostprotocols.net>
2010-05-17 20:06   ` Subrata Modak [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=1274126761.5106.14.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=acme@redhat.com \
    --cc=ltp-list@lists.sf.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