From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Amit Kale <akale@stec-inc.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Announcement: STEC EnhanceIO SSD caching software for Linux kernel
Date: Fri, 11 Jan 2013 23:36:04 +0100 [thread overview]
Message-ID: <20130111223604.GA14144@joi.lan> (raw)
In-Reply-To: <C4B5704C6FEB5244B2A1BCC8CF83B86B07CE4D6F3C@MYMBX.MY.STEC-INC.AD>
On Sat, Jan 12, 2013 at 01:18:37AM +0800, Amit Kale wrote:
> Greetings,
>
> STEC is happy to announce hosting of our EnhanceIO SSD caching software on github.
> We would like to invite kernel hackers to try it. We'll appreciate your
> valuable feedback to help us improve it to the standards of Linux kernel
> source code. We hope to eventually submit it for a possible inclusion in
> Linux kernel.
If you are serious about inclusion in Linux kernel sources, you may want to
act on these comments:
- kernel API wrappers should be removed
- your ioctl won't work with 32-bit userspace on 64-bit kernel (differences
in size and padding of struct cache_rec_short fields)
- volatiles (probably) should go, see Documentation/volatile-considered-harmful.txt
- printk wrappers can be easily replaced by pr_debug/pr_info/etc
- the code should be more or less checkpatch.pl clean
- this is buggy: VERIFY(spin_is_locked((sl))); - spin_is_locked always returns
0 on !CONFIG_SMP && !CONFIG_DEBUG_SPINLOCK
> (...)
> PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED
>
> This electronic transmission, and any documents attached hereto, may contain
> confidential, proprietary and/or legally privileged information. The
> information is intended only for use by the recipient named above. If you
> received this electronic message in error, please notify the sender and delete
> the electronic message. Any disclosure, copying, distribution, or use of the
> contents of information received in error is strictly prohibited, and
> violators will be pursued legally.
FYI, most people are annoyed when they see those kind of threats on public
mailing lists...
Marcin
next prev parent reply other threads:[~2013-01-11 22:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 17:18 Announcement: STEC EnhanceIO SSD caching software for Linux kernel Amit Kale
2013-01-11 22:36 ` Marcin Slusarz [this message]
2013-01-14 21:46 ` Mike Snitzer
2013-01-15 13:19 ` Amit Kale
2013-01-16 10:45 ` [dm-devel] " thornber
2013-01-16 12:15 ` thornber
2013-01-16 16:58 ` thornber
2013-01-17 9:52 ` Amit Kale
2013-01-17 11:39 ` Kent Overstreet
2013-01-17 17:17 ` Amit Kale
2013-01-24 23:45 ` Kent Overstreet
2013-01-17 13:26 ` thornber
2013-01-17 17:53 ` Amit Kale
2013-01-17 18:36 ` Jason Warr
2013-01-18 9:08 ` Amit Kale
2013-01-18 15:56 ` Jason Warr
2013-01-18 16:11 ` thornber
2013-01-18 16:45 ` Jason Warr
2013-01-18 17:42 ` thornber
2013-01-18 17:44 ` Amit Kale
2013-01-18 18:36 ` Jason Warr
2013-01-18 21:25 ` [LSF/MM TOPIC] " Darrick J. Wong
2013-01-18 21:37 ` Mike Snitzer
2013-01-21 5:26 ` Amit Kale
2013-01-21 13:09 ` Mike Snitzer
2013-01-21 13:58 ` thornber
2013-01-22 5:00 ` Amit Kale
2013-02-04 20:33 ` Kent Overstreet
2013-01-18 16:12 ` Amit Kale
2013-01-24 23:55 ` Kent Overstreet
2013-01-17 18:50 ` thornber
2013-01-18 7:03 ` Amit Kale
2013-01-18 14:43 ` thornber
2013-01-30 12:36 ` Pavel Machek
2013-01-30 19:56 ` Amit Kale
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=20130111223604.GA14144@joi.lan \
--to=marcin.slusarz@gmail.com \
--cc=akale@stec-inc.com \
--cc=linux-kernel@vger.kernel.org \
/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