From: Rich Brown <richb.hanover@gmail.com>
To: Paul Spooren <mail@aparcar.org>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] Seeking RPM Server package for OpenWrt
Date: Wed, 23 Mar 2022 08:39:09 -0400 [thread overview]
Message-ID: <4CBEB8E8-0D40-4B25-BCB6-4C4BEA19C751@gmail.com> (raw)
In-Reply-To: <230DF5D9-1784-4077-819D-B4128CB08686@aparcar.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
Hi Paul,
> On Mar 23, 2022, at 8:05 AM, Paul Spooren <mail@aparcar.org> wrote:
>
> The spec wants a 8GB file which seems a bit much for common home routers. We could look into reading from /dev/zero since the body content isn’t relevant but still the device is likely slower at offering the content than your laptop can chew. A dedicated device could be required.
>
> Did you ask upstream about your idea? Maybe they have something in mind already.
Good point. But it's worse than that :-)
It's also possible low-powered CPUs won't be able to keep up with the data stream, so won't achieve saturation...
Still, I figured I would ask for help to see if it might be possible to try. Thanks!
Rich
[-- Attachment #2: Type: text/html, Size: 3069 bytes --]
prev parent reply other threads:[~2022-03-23 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 11:28 Rich Brown
2022-03-23 12:05 ` Paul Spooren
2022-03-23 12:34 ` Bjørn Mork
2022-03-23 12:57 ` Rich Brown
2022-03-23 13:02 ` Paul Spooren
2022-03-23 18:40 ` Christoph Paasch
2022-03-23 19:23 ` Bjørn Mork
2022-03-24 3:58 ` Will Hawkins
2022-03-24 20:15 ` Christoph Paasch
2022-03-23 12:39 ` Rich Brown [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
List information: https://lists.bufferbloat.net/postorius/lists/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CBEB8E8-0D40-4B25-BCB6-4C4BEA19C751@gmail.com \
--to=richb.hanover@gmail.com \
--cc=mail@aparcar.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=rpm@lists.bufferbloat.net \
/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