From: Viktor VM Mihajlovski <mihajlov@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Collin Walling <walling@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Farhan Ali <alifm@linux.ibm.com>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Alexey Kardashevskiy <aik@ozlabs.ru>
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v2 0/4] pc-bios/s390-ccw: Allow network booting via pxelinux.cfg
Date: Wed, 13 Jun 2018 12:56:08 +0200 [thread overview]
Message-ID: <fa6e041f-93a5-905b-dd62-ec525a90b18a@linux.vnet.ibm.com> (raw)
In-Reply-To: <1a67bc9e-b36c-3c88-701f-f47bf5e819f6@redhat.com>
On 12.06.2018 08:17, Thomas Huth wrote:
> On 11.06.2018 14:03, Viktor VM Mihajlovski wrote:
[...]
>
> If you have the time to look at the traffic, could you please also check
> the TFTP block size option that is negotiated at the beginning of the
> TFTP transfer? If this other client is negotiating a transfer block size
> that is bigger than the one from the s390-ccw firmware, this could
> explain the differences in the downloading time, too.
>
> libnet from SLOF currently uses a block size of 1428. This is the size
> where all TFTP data should still fit nicely into one ethernet packet -
> and this is also the size which is still supported by all TFTP servers
> that support the blksize option. But theoretically it's also possible to
> use a bigger block sizes if both, the server and the client support
> fragmented UDP packets. Unfortunately, as far as I can see, SLOF's
> libnet does not support fragmented UDP packets, so we can't increase the
> block size here anymore so easily.
You will be pleased to hear that the SLOF TFTP client outperforms the
busybox version (which uses 544-byte packets) by 30%. There's some
randomness introduced by the differences in DHCP response times which is
clearly not the client's fault. All is good...
[...]
--
Regards,
Viktor Mihajlovski
next prev parent reply other threads:[~2018-06-13 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 12:22 [Qemu-devel] [PATCH v2 0/4] pc-bios/s390-ccw: Allow network booting via pxelinux.cfg Thomas Huth
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 1/4] roms: Update SLOF submodule to current status Thomas Huth
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 2/4] pc-bios/s390-ccw/net: Update code for the latest changes in SLOF Thomas Huth
2018-06-08 7:45 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 3/4] pc-bios/s390-ccw/net: Add support for pxelinux-style config files Thomas Huth
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 4/4] pc-bios/s390-ccw/net: Try to load pxelinux.cfg file accoring to the UUID Thomas Huth
2018-06-07 12:31 ` [Qemu-devel] [PATCH v2 0/4] pc-bios/s390-ccw: Allow network booting via pxelinux.cfg no-reply
2018-06-07 17:01 ` Thomas Huth
2018-06-11 9:08 ` Viktor VM Mihajlovski
2018-06-11 11:12 ` Thomas Huth
2018-06-11 12:03 ` Viktor VM Mihajlovski
2018-06-12 6:17 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-06-13 10:56 ` Viktor VM Mihajlovski [this message]
2018-06-13 11:01 ` Thomas Huth
2018-06-11 9:13 ` [Qemu-devel] " Christian Borntraeger
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=fa6e041f-93a5-905b-dd62-ec525a90b18a@linux.vnet.ibm.com \
--to=mihajlov@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).