-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile error on CentOS(RHEL) 7.3's kernel #165
Comments
Maybe doing things like this would solve the issue but I want first to make clear what is backported. http://dpdk.org/ml/archives/dev/2016-September/046910.html #if (( LINUX_VERSION_CODE >= KERNEL_VERSION(3,19,0) ) \
|| ( RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(7,2) ))
#define HAVE_NDO_DFLT_BRIDGE_ADD_MASK
-#if (!( RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(7,2) ))
+#if ( RHEL_RELEASE_CODE != RHEL_RELEASE_VERSION(7,2) )
#define HAVE_NDO_FDB_ADD_VID
#endif /* !RHEL 7.2 */
#endif /* >= 3.19.0 */ The kernel is basically 3.10 but backports some fragments from the newer kernel is crazy idea. |
@akiradeveloper
I'll running some test right now. BTW, I think there still are some bugs in "Read caching" or other place. Recently we put some physic server into production, in the stress test: sysbench with 64 table, 10M rows each table(150G data, ssd is two 200G 3710), run oltp for 24 hours. 2*6c12t CPU + 64G memory + 600g *6 raid10 HDD with centos 7.2 |
Not sure precisely what was done. Could you please describe about it more? (You can make another issue) If you have the dmesg at the time it would help. |
@bash99 I appreciate your patch that looks good. I want you to make a PR but one question +#define RHEL_RELEASE_VERSION(a,b) (((a) << 8) + (b)) where do you draw this macro from? IOW, how can I believe this is correct? |
@akiradeveloper
|
@akiradeveloper About that bug, dmesg show nothing when mysql lockup, so I'm not so sure about it's a dwb issue and try to reproduce it on aws. |
@bash99 You should have observed the dmesg when "We got a xfs corruption" happened |
It's seem DWB with temporary patch runs fine on AWS ec2. And also works on a two socket bare-metal server (12c24t 64G). @akiradeveloper |
@bash99 Thank you for your efforts. If it's concurrency issue, personally thinking, your system should have exposed it because 24t is enough rich and 72h is enough long to do it. I will wait for the report of running on the product-server. |
Thanks to @bash99 Signed-off-by: Akira Hayakawa <ruby.wktk@gmail.com>
@kazuhisya Could you please test compile with fix-165 branch? I couldn't successfully apply your patch in dm-writeboost-rpm so ported by hand |
Hi, @akiradeveloper dkms: RPM / SRPM When this change is merged into your master, I will also update rpm. |
@kazuhisya Thanks |
Thanks to @bash99 Signed-off-by: Akira Hayakawa <ruby.wktk@gmail.com>
Thanks to @bash99 and @kazuhisya Signed-off-by: Akira Hayakawa <ruby.wktk@gmail.com>
New kernel version, 3.10.0-514.2.2.el7, the old kernel 3.10.0-327.3 is OK.
some output from make.log
As I know, RHEL 7.3 backport some features from new kernel and change some api to kernel 4.4 version.
The text was updated successfully, but these errors were encountered: