# Re: \[PATCH 01/13\] kdbus: add documentation

- From: Ahmed S. Darwish \<hidden\>
- Date: 2015-01-23 06:28:29 
- List: linux-api
- Page: https://ratatoskr.run/linux-api/2015/01/4415878
- Thread: https://ratatoskr.run/linux-api/2015/01/4411688/t.md

```text
On Fri, Jan 16, 2015 at 11:16:05AM -0800, Greg Kroah-Hartman wrote:
> From: Daniel Mack <redacted>
> 
> kdbus is a system for low-latency, low-overhead, easy to use
> interprocess communication (IPC).
> 
> The interface to all functions in this driver is implemented via ioctls
> on files exposed through a filesystem called 'kdbusfs'. The default
> mount point of kdbusfs is /sys/fs/kdbus.

Pardon my ignorance, but we've always been told that adding
new ioctl()s to the kernel is a very big no-no.  But given
the seniority of the folks stewarding this kdbus effort,
there must be a good rationale ;-)

So, can the rationale behind introducing new ioctl()s be
further explained? It would be even better if it's included
in the documentation patch itself.

Thanks,
Darwish
```