public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamal Heib <kamalheib1@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>
Subject: Re: [PATCH for-next] selftests: rdma: Add rdma tests
Date: Thu, 24 Oct 2019 16:39:44 +0300	[thread overview]
Message-ID: <20191024133944.GA20148@kheib-workstation> (raw)
In-Reply-To: <20191024063909.GQ4853@unreal>

On Thu, Oct 24, 2019 at 09:39:09AM +0300, Leon Romanovsky wrote:
> On Wed, Oct 23, 2019 at 11:10:08PM +0300, Kamal Heib wrote:
> > On Wed, Oct 23, 2019 at 02:42:19PM -0300, Jason Gunthorpe wrote:
> > > On Wed, Oct 23, 2019 at 08:39:54PM +0300, Kamal Heib wrote:
> > > > Add a new directory to house the rdma specific tests and add the first
> > > > rdma_dev.sh test that checks the renaming and setting of adaptive
> > > > moderation using the rdma tool for the available RDMA devices in the
> > > > system.
> > >
> > > What is this actually testing? rdmatool?
> > >
> >
> > This is a very basic test that uses the rdmatool for checking two of the
> > RDMA devices functionalities.
> >
> > > This seems like a very strange kselftest to me.
> > >
> >
> > Basically, you can take a look into other subsystems selftests (e.g.
> > net) to see that it not that strange :-).
> 
> Yeah, selftests is in-kernel dumpster, everything goes in. It doesn't
> mean we should follow this path too. The in-kernel tests are great to
> check interfaces and not external tools.
>

OK, I see that you don't like the idea of using external/Userspace tools.

So, what do you suggest?! 

> >
> > Yes, the first test is very basic, but the idea behind it is to utilize
> > the kernel selftests infrastructure to test the rdma subsystem, I plan to
> > introduce more tests in the near future, hopefully other folks from the
> > community will join me too.
> 
> You don't have any version checks, the idea that you can test latest
> kernel features with installed "rdmatool" in distro is a little bit over
> optimistic.
> 
> >
> > Thanks,
> > Kamal
> >
> > > Jason

  reply	other threads:[~2019-10-24 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 17:39 [PATCH for-next] selftests: rdma: Add rdma tests Kamal Heib
2019-10-23 17:42 ` Jason Gunthorpe
2019-10-23 20:10   ` Kamal Heib
2019-10-24  6:39     ` Leon Romanovsky
2019-10-24 13:39       ` Kamal Heib [this message]
2019-10-24 16:11         ` Leon Romanovsky
2019-10-24 12:11 ` Dennis Dalessandro

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=20191024133944.GA20148@kheib-workstation \
    --to=kamalheib1@gmail.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox