All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: Tom Talpey <ttalpey-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>
Cc: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Writes greater than 64k fails with -ENOSPC
Date: Thu, 31 Jan 2013 15:22:15 +0530	[thread overview]
Message-ID: <510A3ECF.2080505@suse.com> (raw)
In-Reply-To: <614F550557B82C44AC27C492ADA391AA044F2E62-Jfd81uAzPQsmBPcf4Gwd0Fir+X/St4rqwBk/1ggFUS45P9zcU8sUGwC/G2K4zDHf@public.gmane.org>

On 01/30/2013 09:36 PM, Tom Talpey wrote:
>> -----Original Message-----
>> From: Jeff Layton [mailto:jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org]
>> Sent: Wednesday, January 30, 2013 9:37 AM
>> To: Tom Talpey
>> Cc: Suresh Jayaraman; linux-cifs
>> Subject: Re: Writes greater than 64k fails with -ENOSPC

>>
>> The spec is not 100% clear on whether servers are *required* to support
>> arbitrarily large writes up to the 128k limit. Clearly there are some that do
>> not, and a larger default is problematic against those servers.
> 
> I'd be very interested to see traces of negotiate, large read and large write from such a server.

I'm not sure whether I can share the complete trace (without customer's
permission) but I can get you the specific bits that might be
interesting. I have asked for a full trace (including negotiate protocol).


Thanks


-- 
Suresh Jayaraman

  parent reply	other threads:[~2013-01-31  9:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 12:24 Writes greater than 64k fails with -ENOSPC Suresh Jayaraman
     [not found] ` <5107BF75.704-IBi9RG/b67k@public.gmane.org>
2013-01-30  0:29   ` Jeff Layton
     [not found]     ` <20130129192913.4942c635-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-01-30 14:06       ` Tom Talpey
     [not found]         ` <614F550557B82C44AC27C492ADA391AA044F2484-Jfd81uAzPQsmBPcf4Gwd0Fir+X/St4rqwBk/1ggFUS45P9zcU8sUGwC/G2K4zDHf@public.gmane.org>
2013-01-30 14:37           ` Jeff Layton
     [not found]             ` <20130130093729.736ad582-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-01-30 16:06               ` Tom Talpey
     [not found]                 ` <614F550557B82C44AC27C492ADA391AA044F2E62-Jfd81uAzPQsmBPcf4Gwd0Fir+X/St4rqwBk/1ggFUS45P9zcU8sUGwC/G2K4zDHf@public.gmane.org>
2013-01-30 17:49                   ` Jeff Layton
     [not found]                     ` <20130130124932.419f2d36-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-01-30 18:07                       ` Tom Talpey
2013-01-31  9:52                   ` Suresh Jayaraman [this message]
     [not found]                     ` <510A3ECF.2080505-IBi9RG/b67k@public.gmane.org>
2013-01-31 11:24                       ` Jeff Layton
     [not found]                         ` <20130131062400.6aa8fb6d-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-02-07  8:52                           ` Suresh Jayaraman
     [not found]                             ` <51136B34.30609-IBi9RG/b67k@public.gmane.org>
2013-02-07 11:50                               ` Jeff Layton
     [not found]                                 ` <20130207065018.0c18868e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-02-07 13:37                                   ` Tom Talpey
     [not found]                                     ` <614F550557B82C44AC27C492ADA391AA044FC781-Jfd81uAzPQsmBPcf4Gwd0Fir+X/St4rqwBk/1ggFUS45P9zcU8sUGwC/G2K4zDHf@public.gmane.org>
2013-02-07 13:55                                       ` Jeff Layton
2013-01-31  9:47       ` Suresh Jayaraman
     [not found]         ` <510A3DB0.1040004-IBi9RG/b67k@public.gmane.org>
2013-01-31 11:21           ` Jeff Layton

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=510A3ECF.2080505@suse.com \
    --to=sjayaraman-ibi9rg/b67k@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ttalpey-0li6OtcxBFHby3iVrkZq2A@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 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.