Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>
To: Yale Zhang <yzhang1985-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: strange bottleneck with SMB 2.0
Date: Thu, 20 Aug 2015 08:57:01 -0400	[thread overview]
Message-ID: <20150820085701.46611da1@tlielax.poochiereds.net> (raw)
In-Reply-To: <CALQF7Zw5ET+uhgskMDMar31q1uo98nkSd9dusX4gQpS47-zKig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, 19 Aug 2015 04:11:31 -0700
Yale Zhang <yzhang1985-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> SMB developers/users,
> 
> I'm experiencing a strange bottleneck when my files are mounted as SMB
> 2.0. When I launch  multiple processes in parallel for benchmarking,
> only the 1st one starts, and the rest won't start until the 1st one
> finishes:
> 
> ---------------------------------------test
> programs--------------------------------
> #!/bin/sh
> ./a.out&
> ./a.out&
> ./a.out&
> wait
> 
> a.out is just a C program like this:
> 
> int main()
> {
>   printf("greetings\n");
>   while (true);
>   return 0;
> }
> 
> Apparently, this only affects SMB 2.0. I tried it with SMB 2.1, SMB
> 3.0, & SMB 3.02, and everything starts in parallel as expected.
> 
> I'm assuming SMB 3 and especially SMB 2.1 would share a common
> implementation. How could 2.0 have the problem but not 3? It almost
> seems the bottleneck is a feature instead of a bug?  8(
> 
> Can it still be fixed?
> 
> -Yale

Probably. It'd be interesting to see what the other tasks are blocking
on. After firing up the second one can you run:

    # cat /proc/<pid of second a.out>/stack

...and paste the stack trace here? That should tell us what those other
processes are doing.

-- 
Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>

  parent reply	other threads:[~2015-08-20 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 11:11 strange bottleneck with SMB 2.0 Yale Zhang
     [not found] ` <CALQF7Zw5ET+uhgskMDMar31q1uo98nkSd9dusX4gQpS47-zKig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-19 12:40   ` Steve French
2015-08-20 12:57   ` Jeff Layton [this message]
     [not found]     ` <20150820085701.46611da1-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2015-09-29  0:09       ` Yale Zhang
     [not found]         ` <CALQF7Zz63RFF6C4YW8C0-spwHju=BTCDcyKtvAUh_0Lhe=Xseg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-29  0:18           ` Steve French
     [not found] ` <CAH2r5mu3xF2NLU_cTx6BwcYmLHHcpNm8_x_sdkFNhCmM8CF=Kw@mail.gmail.com>
     [not found]   ` <CAH2r5mu3xF2NLU_cTx6BwcYmLHHcpNm8_x_sdkFNhCmM8CF=Kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-19 13:41     ` Yale Zhang

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=20150820085701.46611da1@tlielax.poochiereds.net \
    --to=jlayton-vpemndpepfumzcb2o+c8xq@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yzhang1985-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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