Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <ath6kl-devel@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <mjei78@gmail.com>
Subject: Re: [PATCH] ath6kl: Fix the byte alignment rule to avoid loss of bytes in a TCP segment
Date: Mon, 18 Mar 2013 13:54:53 +0200	[thread overview]
Message-ID: <87d2uw9b3m.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20130310061605.27321.89150.stgit@localhost6.localdomain6> (Kalle Valo's message of "Sun, 10 Mar 2013 08:16:05 +0200")

Kalle Valo <kvalo@qca.qualcomm.com> writes:

> From: Myoungje Kim <mjei78@gmail.com>
>
> Either first 3 bytes of the first received tcp segment or last one
> over MTU size file can be loss due to the byte alignment problem.
> Although ATH6KL_HTC_ALIGN_BYTES was defined for 'extra bytes for htc header
> alignment' in the patch "Fix buffer alignment for scatter-gather
> I/O"(1df94a857), there exists the bytes loss issue which means that it will be
> truncated 3 bytes in the transmitted file contents if a file which has over MTU
> size is transferred through TCP/IP stack.  It doesn't look like TCP/IP stack
> bug of 3.5 or the latest version of kernel but the byte alignment issue.  This
> patch is to use the roundup() function for the byte alignment rather than the
> predefined ATH6KL_HTC_ALIGN_BYTES.
>
> kvalo: fixed indentation
>
> Signed-off-by: Myoungje Kim <mjei78@gmail.com>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>

Thanks, applied.

-- 
Kalle Valo

      reply	other threads:[~2013-03-18 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10  6:16 [PATCH] ath6kl: Fix the byte alignment rule to avoid loss of bytes in a TCP segment Kalle Valo
2013-03-18 11:54 ` Kalle Valo [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=87d2uw9b3m.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mjei78@gmail.com \
    /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