public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] Implement /dev/byte (a generic byte source similiar to /dev/zero)
Date: Tue, 19 Apr 2011 10:34:04 +0200	[thread overview]
Message-ID: <4DAD48FC.5040003@ahsoftware.de> (raw)
In-Reply-To: <BANLkTi=yaXOWnUi2s1A-BtoAFgjExX8q4w@mail.gmail.com>

Am 18.04.2011 15:57, schrieb Mike Frysinger:
> On Mon, Apr 18, 2011 at 07:37, Alexander Holler wrote:
>> I don't know if this patch qualifies for inclusion into the mainline kernel, but
>> maybe someone else would be interested in such, so I'm posting it here.
>>
>> The main idea for that device was to have a source for 0xff to clear FLASH based
>> devices. And to make it more generic, I've added the possibility to change the
>> default value on a per file descriptor basis.
>>
>> I don't want to discuss if such a device makes sense or if such should be done
>> in userspace only. I like it as a device, otherwise I wouldn't have written it.
>> So besides this message, I will not take part in such a discussion.
>
> cant you do this with cuse ?  that would satisfy the "has to be a
> device" requirement while keeping it in userspace.

I know almost nothing about cuse, but I assume it should be possible to 
build such a device with cuse too.

> although, i have a hard time seeing there be a realistic perf diff with:
> tr '\000' '\377'<  /dev/zero | dd ......

There are many other ways to achieve such in userspace (even without 
using /dev/zero) and I want to avoid such a discussion.

As for /dev/zero there are many other possible reasons to use such a 
device, besides filling something with a value. For me it's as 
reasonable as dev/zero, just that it offers a bit more flexibility and 
provides another, at least for me useful, default value. Maybe 
/dev/nzero would have been a good name too. ;)

But I don't really care about inclusion into the kernel, it's just 
something I had lying around (and needed only marginally work to 
finalize as a proper patch) and I thought someone else could find it 
usefull and I should share that here.

Regards,

Alexander Holler

  reply	other threads:[~2011-04-19  8:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 11:37 [PATCH 0/1] Implement /dev/byte (a generic byte source similiar to /dev/zero) Alexander Holler
2011-04-18 11:37 ` [PATCH 1/1] " Alexander Holler
2011-04-20 10:57   ` Pavel Machek
2011-04-20 18:07     ` Alexander Holler
2011-04-18 13:57 ` [PATCH 0/1] " Mike Frysinger
2011-04-19  8:34   ` Alexander Holler [this message]
2011-04-19  8:44     ` Alan Cox
2011-04-19  9:05       ` Alexander Holler
2011-04-19  9:32         ` Alexander Holler

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=4DAD48FC.5040003@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier.adi@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