From: Mischa Baars <mjbaars1977.linux-block@cyberfiber.eu>
To: Laurence Oberman <loberman@redhat.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: packet writing support
Date: Mon, 07 Oct 2019 11:02:58 +0200 [thread overview]
Message-ID: <7d2e7b926a3a329e8526cd5c1f26d56dcb54d933.camel@cyberfiber.eu> (raw)
In-Reply-To: <a5c5b4da389e43ac4fb6960135f634a6e2b8ee13.camel@redhat.com>
On Sun, 2019-10-06 at 16:48 -0400, Laurence Oberman wrote:
> On Sun, 2019-10-06 at 10:31 +0200, Mischa Baars wrote:
> > On Sat, 2019-10-05 at 09:50 -0600, Jens Axboe wrote:
> >
> > > It's not really a case of quid pro quo, if someone gets removed,
> > > something else can stay. I'd argue that the floppy driver is
> > > probably
> > > used by orders of magnitude more people than the packet writing
> > > code,
> > > and as such that makes it much more important to maintain.
> >
> > I'm not into time-reversal, if that is what you mean?! I love
> > unilinear time and causal computers!
> >
> > Regards,
> > Mischa.
> >
>
> Hello Mischa
> Something is not making sense here.
> If this will not be an open source project and not released then why
> not simply snapshot the kernel as is now and go ahead.
> Maintain it yourself, issue solved. No need to harp on the packet
> writing code support anymore.
>
> Many companies have taken a snap of the kernel to use for storage
> arrays and then made changes and did not release the entire solution as
> open source.
>
> You said
>
> "Yes, I've written the the code myself, thank you. It's prototype
> hardware and it's not intended as an open source software project. It
> is therefore not going to
> be released to the general public. When it's finished, and it isn't at
> the moment, it's hopefully going to be part of your future processors.
> "
>
Actually I was saying something entirely different, wasn't I?
> Regards
> Laurence Oberman
Regards,
Mischa.
next prev parent reply other threads:[~2019-10-07 9:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 10:12 packet writing support Mischa Baars
2019-10-05 15:50 ` Jens Axboe
2019-10-06 7:31 ` Mischa Baars
2019-10-06 15:10 ` Jens Axboe
2019-10-07 7:02 ` Mischa Baars
2019-10-07 7:23 ` Hannes Reinecke
2019-10-07 8:07 ` Mischa Baars
2019-10-07 8:45 ` Hannes Reinecke
2019-10-07 9:11 ` Mischa Baars
2019-10-07 9:17 ` Mischa Baars
2019-10-07 14:22 ` Bart Van Assche
2019-10-07 14:36 ` Mischa Baars
2019-10-07 16:13 ` Mischa Baars
2019-10-07 16:19 ` Jens Axboe
2019-10-07 17:31 ` Mischa Baars
2019-10-07 10:02 ` Hannes Reinecke
2019-10-07 14:10 ` Jens Axboe
2019-10-07 14:19 ` Mischa Baars
2019-10-06 8:31 ` Mischa Baars
2019-10-06 20:48 ` Laurence Oberman
2019-10-07 8:10 ` Mischa Baars
2019-10-07 9:02 ` Mischa Baars [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-04 9:22 Mischa Baars
2019-10-04 9:21 Mischa Baars
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=7d2e7b926a3a329e8526cd5c1f26d56dcb54d933.camel@cyberfiber.eu \
--to=mjbaars1977.linux-block@cyberfiber.eu \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=loberman@redhat.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 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.